# 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. Source: https://elaichi.ai/connectors/ironclad/ ## Facts | | | | --- | --- | | Application | Ironclad | | Category | E Signature | | AI tools | 13 | | Authentication | Connects over OAuth | | Needs your own OAuth app | Yes | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Ironclad is connected - 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. ## Connect Ironclad in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Ironclad. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Ironclad tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Ironclad to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Ironclad to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Ironclad tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Ironclad through Elaichi ### Kick off an NDA right after the call Sales. 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. ### See every contract request in flight Legal. 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. ### Cancel a duplicate or stale request Legal. When a deal dies or someone submitted the same agreement twice, cancel the extra Ironclad workflow from the chat and keep the pipeline honest. ### Start vendor agreements from a shortlist Procurement. Turn a list of chosen suppliers into vendor agreement workflows in Ironclad, each with the right counterparty, term, and owner attached from the start. ### Check what each contract type asks for Legal operations. 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. ### Keep the Ironclad user list clean IT. 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. ## 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 my team share one Ironclad connection? Yes. One admin connects Ironclad in Elaichi and shares the connection with a team, and nobody else ever handles the client ID, secret, or any credential. Each teammate still signs in to Elaichi as themselves, so every workflow started or cancelled in Ironclad is logged under the name of the person who did it. ### 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. ## All 13 Ironclad tools Every tool below is callable through https://api.elaichi.ai/mcp once Ironclad is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Ironclad workflows** (List). Retrieves the workflows in your Ironclad account. Each workflow object in the response includes key details such as the id, title, associated template, current step, status, creation and update timestamps, and information about the workflow creator. It also includes structured schema definitions for all fields used in the workflow, and the attributes object contains the values submitted for the fields in the workflow. - **Get single Ironclad workflow by ID** (Get). Retrieves the data associated with a specific workflow in your Ironclad account. It always requires ID to fetch. - **Create a Ironclad workflow** (Create). Use this endpoint to launch/create a new Workflow synchronously. - **Ironclad workflows cancel** (Cancel). Cancel a workflow by id in Ironclad. Requires a comment object in the request body. Returns the canceled workflow details including status and cancellation reason. - **List all Ironclad users** (List). Retrieves the users from your Ironclad account via SCIM. The response includes each user's basic details such as ID, name, email, job title, status, group memberships, and metadata like creation and last modified timestamps. - **Get single Ironclad user by ID** (Get). Retrieves the information of a single user from your Ironclad account via SCIM. It always requires ID to fetch. - **Delete a Ironclad user by ID** (Delete). This endpoint will delete a single user from your Ironclad account. It always requires ID to delete. If the deletion is successful, all active workflows associated with the deleted user should be automatically reassigned to the default user within the admin group. - **List all Ironclad groups** (List). Retrieves the list of user groups from your Ironclad account via SCIM. The response includes each group's details, such as the group ID, display name, and metadata like the resource type and location URL. The response also contains a list of group members. - **Get single Ironclad group by ID** (Get). Retrieves the information of a single group from your Ironclad account via SCIM. It always requires ID to fetch. - **List all Ironclad me** (List). Retrieves basic profile information about the authenticated user in Ironclad. The response includes their unique ID (id or sub), email address, name (firstName, lastName, displayName), job title, and the company they belong to (companyId, companyName). - **List all Ironclad workflow schemas** (List). Returns a list of workflow schemas. Each schema specifies the fields used in the workflow's launch form. Use the form query param to specify the launch form. - **Get single Ironclad workflow schema by ID** (Get). Retrieves a single workflow schema from your Ironclad account. It always requires ID to fetch. - **Create a Ironclad async workflow** (Create). Use this endpoint to launch/create a new Workflow asynchronously for non-blocking performance, which is helpful when/if you provide files to the Workflow.