E Signature
Ironclad MCP connector
The Ironclad connector lets Claude, ChatGPT, Cursor, and other MCP clients start, check, and cancel contract workflows in Ironclad, and look up its users and groups, with each person working inside their own Ironclad access.
-
How it connects. Connects over OAuth. 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.
13 tools
How to connect
How to connect Ironclad to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Ironclad once
-
Open Connections, choose Add connection, and pick Ironclad.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Ironclad app, then approve. Ironclad needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
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 Ironclad 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 Ironclad 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 Ironclad 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 Ironclad 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 Ironclad through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Kick off an NDA right after the call
Ask for a new NDA or order form workflow for the prospect you just spoke to, filled in from what Ironclad already needs for that contract type, without opening Ironclad yourself.
-
Legal
See every contract request in flight
Get a plain list of open Ironclad workflows, who requested them, and how far along each one is, so the morning triage takes minutes instead of a tour through the queue.
-
Legal
Cancel a duplicate or stale request
When a deal dies or someone submitted the same agreement twice, cancel the extra Ironclad workflow from the chat and keep the pipeline honest.
-
Procurement
Start vendor agreements from a shortlist
Turn a list of chosen suppliers into vendor agreement workflows in Ironclad, each with the right counterparty, term, and owner attached from the start.
-
Legal operations
Check what each contract type asks for
Ask which workflow types exist in Ironclad and which fields each one requires, so intake forms, playbooks, and training stay in step with what the system actually collects.
-
IT
Keep the Ironclad user list clean
Review who has an Ironclad account, which groups they sit in, and remove people who have moved on, all from one place alongside the rest of your access reviews.
Try asking
- “Which Ironclad workflows are still awaiting signature this week?”
- “List Ironclad workflows created from the NDA workflow schema.”
- “Show Ironclad groups and the users in each one.”
AI tools
Ironclad tools for your AI agents
13 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ironclad, 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 Ironclad gets you
6 screens from the product, each doing one job for your Ironclad account.
The agent
Ask about Ironclad workflows in plain language.
Three starter prompts pull answers from live Ironclad workflows, users and groups.
- workflows
- workflow schemas
- users
- groups
Ask Elaichi to work across your apps.
Which Ironclad workflows are still awaiting signature this week?
List Ironclad workflows created from the NDA workflow schema.
Show Ironclad groups and the users in each one.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Ironclad here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
13 Ironclad tools ready without custom code.
Workflows, workflow schemas, users and groups, each with listed resources and methods.
- List all Ironclad workflows
- Get single Ironclad workflow by ID
- Create a Ironclad workflow
- Ironclad workflows cancel
ElaichiToolsToolboxes
Every team gets its own Ironclad toolbox.
Legal, Sales and Finance each see the Ironclad tools scoped to them.
- Legal
- Sales
- Procurement
- Finance
ElaichiToolboxesShared connections
Teammates run Ironclad workflows without a credential.
Each Ironclad connection shows who connected it and which teams and members share it.
- Legal Ops
- Sales EMEA
- Procurement
- Finance
ElaichiConnectionsAudit log
Every Ironclad call is written down.
When, who, what happened, type and resource, appended for each workflow action.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 Ironclad workflow digest.
Six steps fetch and group workflows, an agent drafts, a person approves, Ironclad receives it.
Ironclad digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch workflows
Ironclad
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
Ironclad
Queued
Collections and dashboards
Ironclad workflow health, counted not guessed.
Four metrics, 14 days of workflows created and a team breakdown, refreshed on schedule.
Ironclad health
Refreshed 4 minutes ago · every 15 minutes · from the workflows collection
Workflows
1,284 ↓ 12%
Workflow schemas
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Workflows created
Last 14 days
By team
Share of activity
Legal Ops 34%
Sales EMEA 27%
Procurement 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Ironclad to Claude?
Two steps. First, connect Ironclad in Elaichi: Ironclad asks you to register an OAuth application inside Ironclad once, so an admin brings a client ID and secret one time, then signs in with their normal Ironclad login. Second, open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in as yourself and Ironclad is ready to use.
Does Ironclad work with ChatGPT and Cursor as well as Claude?
Yes. Once Ironclad 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 Ironclad once and every client sees it.
What can an AI agent actually do with my Ironclad data?
It can start a new contract workflow in Ironclad, such as an NDA or vendor agreement, using the fields that contract type requires, and it can list open workflows, pull up a single one, or cancel one that is no longer needed. It can also tell you which workflow types your Ironclad has, who your Ironclad users are, which groups they belong to, and who you are signed in as. It does not edit contract language or sign anything; it moves requests through the process you already run in Ironclad.
Does connecting Ironclad give the AI access to every contract and workflow?
No. Each person signs in to Ironclad as themselves, so an agent working for them sees only the workflows, users, and groups that person can already see in Ironclad. Elaichi can narrow that further with restrictions, for example allowing viewing but not creating, and it can never widen access beyond what Ironclad has granted the person.
Can I stop an agent from cancelling or changing things in Ironclad?
Yes. Restrictions in Elaichi work per action, so you can allow an agent to list and read Ironclad workflows while blocking it from creating workflows, cancelling them, or deleting Ironclad users. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to an Ironclad connection when someone leaves?
Offboarding a person in Elaichi ends their access to Ironclad through every client at once. If they were using a shared Ironclad connection, it keeps working for everyone else on the team. If you want Ironclad gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Ironclad in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.