Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Firma.dev in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Firma.dev e-signature from any AI agent: templates, signing requests from a template, sending and reminders, recipient status, audit trail and signed PDFs. 13 tools, API-key auth, with free test keys.
Try asking
Example prompts for Firma.dev
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Firma.dev, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Firma.dev + Gemini
Firma.dev e-signature from any AI agent: templates, signing requests from a template, sending and reminders, recipient status, audit trail and signed PDFs. 13 tools, API-key auth, with free test keys.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
FIRMA_API_KEY
Step 1 — Get credentials
This connector drives Firma.dev (api.firma.dev), a developer-first e-signature API: templates, signing requests (envelopes), their recipients, audit trail and signed documents. 13 tools.
Setup
- Sign up at https://firma.dev (free, no card) and open your workspace in the dashboard.
- Copy an API key into
FIRMA_API_KEY. Every workspace has two: the test key creates watermarked test requests and consumes no credits, the live key sends real, legally binding requests and consumes one credit per envelope (about €0.049). Start with the test key. - The key is sent as the
Authorizationheader, without a Bearer prefix. It is stored encrypted.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Gemini
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Gemini CLI reads MCP servers from ~/.gemini/settings.json (or %APPDATA%\gemini\settings.json on Windows). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Get your MCP API key from AnythingMCP → MCP Servers → your server → API keys.
- Save the file and restart
gemini. - Run
/mcpinside the Gemini CLI —Firma.devshould be listed as available. - Vertex AI Studio: pass
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_IDto thetoolsarray of your request with the sameX-API-Keyheader.
Available tools
| Tool | What it does |
|---|---|
firma_get_company | The Firma.dev company account behind the key: name, owner, language and the remaining envelope credits |
firma_list_templates | List the workspace's templates (reusable documents with recipient slots and fields), newest first unless sorted otherwise |
firma_get_template | One template in full: its settings, document, fields and reminders, as it would be copied into a signing request |
firma_list_template_recipients | The recipient slots of a template: id (pass it as template_user_id when creating a signing request), designation (Signer, Approver, CC)… |
firma_list_signing_requests | List signing requests (envelopes) with their status and dates, filtered by status, name, signer or creation date |
firma_get_signing_request | One signing request in full: status flags (sent, finished, cancelled, declined, expired), timestamps, expiry, credit cost and settings |
firma_list_signing_request_recipients | The recipients of a signing request with where each one stands: finished_on (signed), declined_on and decline_reason, signing order, and… |
firma_get_signing_request_audit | The audit trail of a signing request in chronological order: created, edited, sent and cancelled by the sender; viewed, signed, declined… |
firma_get_signed_document_url | A short-lived download URL for the signed PDF of a finished signing request (or the partially signed PDF when partial download is enabled) |
firma_create_signing_request_from_template | Create a DRAFT signing request from a template, with the real recipients filled into the template's slots |
firma_send_signing_request | Send a draft signing request: every signer gets the signing email |
firma_resend_signing_request | Email the signing link again to recipients who can sign now and have not signed yet, optionally with a short message |
firma_cancel_signing_request | Cancel a sent signing request that is not finished yet; signers can no longer sign it |
FAQ
Does Gemini 1.5 Pro or 2.x support MCP? Yes — Gemini CLI ≥ 0.4 and Vertex AI tools API both accept MCP httpUrl connectors with custom headers.
Next steps
Was this guide helpful?
