E Signature
Firma MCP connector
The Firma connector brings signing requests, templates, workspaces and companies into Claude, ChatGPT, Cursor or any MCP client, so your team can prepare, send and track documents for signature from a conversation, inside each person's own Firma access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Firma to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Firma once
-
Open Connections, choose Add connection, and pick Firma.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Firma API key. One person generates a token in Firma and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Firma to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Firma to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Firma to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Firma to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Firma through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Send the contract before the call ends
Pick the right Firma template, fill in the customer's details and send the signing request while the deal is still warm. The rep never leaves the conversation to do it.
-
Sales
See which contracts are still unsigned
Ask for every open signing request this week and find out which ones are waiting on the customer. Chase the right people instead of scrolling through the Firma dashboard.
-
HR
Get offer letters out the same day
Create a signing request from the offer letter template, drop in the candidate's name, title and start date, and send it. Cancel and reissue if the terms change before they sign.
-
Legal
Keep the NDA template current
Update the standard NDA in Firma, duplicate it for a regional variant, and check which fields and signers each version expects. Retire old templates so nobody sends them by mistake.
-
Finance
Track vendor agreements through to signature
List the signing requests tied to a supplier onboarding, check where each one stands, and cancel any that were sent against the wrong terms. Reminder settings on each template are visible too.
-
Operations
Set up a workspace for a new team
Create a Firma workspace for a new office or business unit, keep company details up to date, and see which templates and users belong where. Everything lands in the audit log.
Try asking
- “Which Firma templates changed in the last 30 days?”
- “List Firma workspaces with no templates attached.”
- “Show Firma companies added this quarter and their workspaces.”
AI tools
Firma tools for your AI agents
48 tools are ready to call through Elaichi's MCP endpoint the moment you connect Firma, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Firma gets you
6 screens from the product, each doing one job for your Firma account.
The agent
Ask about Firma templates, get real answers.
Plain language questions answered from live Firma companies, workspaces and templates.
- companies
- workspaces
- templates
- documents
Ask Elaichi to work across your apps.
Which Firma templates changed in the last 30 days?
List Firma workspaces with no templates attached.
Show Firma companies added this quarter and their workspaces.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Firma here.
One governed MCP endpoint for Firma over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
48 Firma tools are ready to call.
Browse Firma companies, workspaces and template methods without writing custom code.
- List all Firma companies
- Update a Firma company by ID
- Firma companies partial update
- List all Firma workspaces
Toolboxes
Every team gets its own Firma toolbox.
Curate toolboxes so Legal, Sales and HR each see the Firma tools they need.
- Legal
- Sales
- People
- Finance
Shared connections
Teammates sign through Firma without credentials.
See who connected each Firma account and which teams and members share it.
- Legal
- Sales EMEA
- People Ops
- Finance
Audit log
Every Firma call is written down.
When, who, what happened, type and resource for each template and workspace action.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Firma digest.
Firma templates are fetched, grouped, drafted by an agent, approved, then posted back.
Firma digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch companies
Firma
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Firma
Queued
Collections and dashboards
Firma numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Firma health
Refreshed 4 minutes ago · every 15 minutes · from the companies collection
Companies
1,284 ↓ 12%
Workspaces
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Companies created
Last 14 days
By team
Share of activity
Legal 34%
Sales EMEA 27%
People Ops 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Firma to Claude?
Connect Firma in Elaichi first, which asks you to paste the API key from your Firma account settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. Sign in as yourself and Firma is ready to use in Claude.
Does Firma work with ChatGPT and Cursor as well as Claude?
Yes. Once Firma is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Firma once and every client sees it.
What can an AI agent actually do with my Firma data?
With Firma connected, an agent can list your signing requests and check where each one stands, create a new signing request from a template and send it, update one before it goes out, or cancel one that was sent in error. It can also create, update, duplicate and delete templates, look up the fields, signers and reminder settings on a template, and manage workspaces and company details. Short, concrete asks such as "send the NDA template to [email protected]" work better than long instructions.
Does connecting Firma give the AI access to every workspace and template?
No. Every call to Firma runs inside the access of the person who signed in, so an agent sees only the workspaces, templates and signing requests that person can already see in Firma. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Firma itself allows that person.
Can I stop an agent from deleting or changing things in Firma?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and sending Firma signing requests while blocking template deletion, cancellation or any updates. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
What happens to a Firma connection when someone leaves?
Offboarding a person in Elaichi ends their access to Firma through every connected client at once. If they had shared a Firma connection with a team, it keeps working for everyone else. Disconnecting Firma once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Firma in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.