Ironclad MCP connector
The Ironclad connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects over OAuth
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Which Ironclad workflows are still awaiting signature this week?
Working in Ironclad with Elaichi
-
List all Ironclad workflows
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Ironclad to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Ironclad MCP connector for 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.
Ironclad MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Ironclad MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Ironclad MCP connector for 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.
Ironclad MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Ironclad through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Ironclad is logged.
-
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.”
What connecting Ironclad gets you
6 screens from Elaichi, each doing one job for your Ironclad account.
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, Cursor or Microsoft Copilot
The agent
Ask about Ironclad workflows in plain language.
Three starter prompts pull answers from live Ironclad workflows, users and groups.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Ironclad here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
13 Ironclad tools ready without custom code.
Workflows, workflow schemas, users and groups, each with listed resources and methods.
ElaichiToolboxesToolboxes
Every team gets its own Ironclad toolbox.
Legal, Sales and Finance each see the Ironclad tools scoped to them.
ElaichiConnectionsShared connections
Teammates run Ironclad workflows without a credential.
Each Ironclad connection shows who connected it and which teams and members share it.
ElaichiAudit logAudit log
Every Ironclad call is written down.
When, who, what happened, type and resource, appended for each workflow action.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Ironclad digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Ironclad
Queued
Automations
A schedule drafts your Ironclad workflow digest.
Six steps fetch and group workflows, an agent drafts, a person approves, Ironclad receives it.
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%
Collections and dashboards
Ironclad workflow health, counted not guessed.
Four metrics, 14 days of workflows created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Ironclad
All three can connect Ironclad to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Ironclad tools | Allow or restrict single Ironclad tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Ironclad call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting it from creating workflows, cancelling them, or deleting Ironclad users. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client at the same time.
Does the Ironclad MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Ironclad is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Ironclad?
Yes. Both let Claude, ChatGPT or Cursor use Ironclad. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Ironclad call.
How is Elaichi different from Composio for Ironclad?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Ironclad: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Ironclad in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot