Firma lets you add legally binding e-signatures to anything you build with Claude Code. Connect Firma’s MCP servers and Claude Code can generate accurate Firma integration code, manage your signing requests, and operate on your Firma data directly from the terminal or your IDE.Documentation Index
Fetch the complete documentation index at: https://docs.firma.dev/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A Firma account with an API key
- Claude Code installed (CLI, VS Code extension, or JetBrains plugin)
- At least one Firma template with signing fields configured
Firma uses the raw API key as the
Authorization header value - do not prefix it with Bearer. This differs from many other APIs.Getting started
Step 1: Add the Firma MCP servers
Add both Firma MCP servers to your project settings. In your project root, create or edit.claude/settings.json:
~/.claude/settings.json to make them available across all projects.
- firma-api gives Claude Code direct access to the Firma API - 84 tools across signing requests, templates, workspaces, and webhooks.
- firma-docs gives Claude Code access to Firma’s full documentation so it generates accurate integration code.
When to use which server:
firma-api is for doing things (sending signing requests, managing templates). firma-docs is for building things (generating integration code with accurate API details). Most developers want both connected.Step 2: Use Firma from Claude Code
Once connected, you can ask Claude Code to build Firma integrations or operate on your data: Generate a backend integration:firma-docs MCP server before writing code. Without that, it may fall back to general knowledge and miss endpoint or auth details.
What Claude Code generates
When you ask Claude Code to build a Firma integration, the generated backend code should look like this:create-and-send endpoint creates the signing request and sends it to recipients atomically. If you need to review or modify the request before sending, use POST /signing-requests to create a draft, then POST /signing-requests/{id}/send separately.
Webhook integration
To track signing events in real time, ask Claude Code to add a webhook handler:Embedded signing
For apps where signers complete documents inside your UI instead of opening a Firma-hosted page, thecreate-and-send response includes first_signer.id (the signing_request_user_id) and a ready-made first_signer.signing_link. Load the signer URL in an iframe:
Tips
- Use
firma-docswhen building,firma-apiwhen operating. The docs server helps Claude Code write correct integration code. The API server lets it manage signing requests, templates, and workspaces directly. - Pass
template_idexplicitly. Templates are the safest way to constrain what the agent can send. - Validate before sending. For higher-stakes documents, ask Claude Code to create a draft with
POST /signing-requests, then confirm before callingPOST /signing-requests/{id}/send. - Workspaces for multi-tenant apps. If you are building a SaaS product, give each end customer their own Firma workspace so templates and usage stay isolated.
Next steps
- API authentication - API keys and workspace scoping
- Webhooks guide - Event types, payloads, and signature verification
- Embedded signing - In-app signing experience
- Creating workspaces - Multi-tenant setups for SaaS apps
- MCP integration - Full MCP server reference with all 84 tools
- Complete setup guide - End-to-end Firma integration walkthrough
- API reference - Full endpoint documentation