# Ironclad MCP Server & Agent Skill > Source: https://ibl.ai/developer/connectors/ironclad Connector · Contract lifecycle management system Last updated: October 20, 2026 **ibl.ai publishes a free Ironclad agent skill: a SKILL.md that teaches an AI agent to read and write Ironclad data and expose it as an MCP tool. Download it, connect your own Ironclad credentials, and run the agent on ibl.ai Agentic OS, where you own all the code and the data.** Ironclad is contract lifecycle management software. Workflows run contracts through drafting, approval and signature; completed contracts become records in the repository with metadata, attachments, entities and obligations. ## What is the Ironclad API, and what can an agent read from it? REST endpoints under /public/api/v1 for workflows (launch, approvals, comments, signatures), records (CRUD, attachments, schema), entities, obligations, webhooks and data exports, plus a SCIM API for users and groups. - API: Ironclad Public API (REST) - Access: Issued by your administrator - Base URL: https://ironcladapp.com/public/api/v1/ (check your account's domain; sandbox instances differ) - Authentication: OAuth 2.0 authorization code; OAuth 2.0 client credentials; Legacy bearer access token An Ironclad customer registers an OAuth client application in Ironclad. The /exports endpoint needs the Security & Data Pro add-on, bought through the Ironclad account team. OAuth 2.0 bearer tokens with per-endpoint scopes, e.g. public.records.readRecords, public.workflows.createWorkflows. Legacy access tokens still work, with a published migration guide to OAuth 2.0. ### What can an agent read from Ironclad? - **Records** — List all records with filters, retrieve a record and its attachments, retrieve the records schema. - **Workflows** — List or retrieve workflows, workflow schemas, approvals, turn history and sign-step status. - **Entities** — List and retrieve counterparty entities and relationships. - **Obligations** — Contract obligations and recurring instances. - **Data exports** — Create and download exports (Security & Data Pro add-on only). ### What can an agent write to Ironclad? - **Workflows** — Launch a workflow synchronously or asynchronously, update approval status, add comments. - **Signature requests** — Send or cancel signature requests, remind or update signers. Confirm with the user first. - **Records** — Create a record or replace a record's metadata. - **Records (delete)** — Delete an existing record (scope public.records.deleteRecords). Confirm with the user first. Limits: Per-company buckets in requests per minute, e.g. workflows read 400, workflows write 40, records read 600, records write 200, MCP 80; company-wide cap 4,500 RPM. 429 includes Retry-After; X-RateLimit-* headers returned. Contracts, negotiation history and approval comments are confidential business and client information and may be privileged when prepared with counsel. ## How do I connect Ironclad to an AI agent over MCP? Ironclad publishes an official MCP server: [Ironclad MCP server](https://ironcladapp.com/resources/articles/mcp-integrations). Ironclad-run MCP server, live since July 2026 for Claude, ChatGPT and Slackbot. Answers contract and workflow questions via Ironclad Assistant, scoped to each user's permissions. You can register that server on ibl.ai as it is, or use the SKILL.md below when you want the agent to call the Ironclad Public API directly. On ibl.ai an MCP connection is three records, and a working integration always needs all three: 1. **Register the server** — `POST …/mcp-servers/` with its URL, a transport (`sse`, `websocket` or `streamable_http`) and an `auth_type` of `none`, `token` or `oauth2`. 2. **Create a connection** that holds the credential, scoped to the whole organization (`platform`), to a single agent, or to each user (`user`). 3. **Enable it on the agent** — `mcp-tool` in `tool_slugs` and the server id in `mcp_servers`. Both lists are replaced, not merged, so read the settings first. Ironclad supports per-user OAuth, so the server can use `auth_type=oauth2` with `auth_scope=user`: each person connects their own Ironclad account in the chat the first time the agent needs it. The field reference is in [MCP server connections](https://ibl.ai/developer/platform/mcp/mcp-connections), and the [/iblai-api-agent-mcp](https://ibl.ai/developer/skills/iblai-api-agent-mcp) skill runs all three steps from a coding agent. ## What does the Ironclad agent skill do? The Ironclad skill is one SKILL.md file named `iblai-connect-ironclad`. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails. [Download the Ironclad SKILL.md](https://ibl.ai/developer/connectors/ironclad/SKILL.md) Save it as `.claude/skills/iblai-connect-ironclad/SKILL.md`, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install: ``` npx skills add iblai/vibe --all ``` This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository. It was checked against Ironclad's documentation on October 20, 2026. Test it against your own Ironclad setup before you rely on it. ### What can I ask an Ironclad agent to do? - “Do we have a signed NDA with Acme Corp?” - “Show MSAs signed in the last six months that cap liability” - “Where is the Johnson deal stuck in approvals?” - “Launch an NDA workflow for Beta Inc. with jane@beta.com as signer” ## How do I run an Ironclad agent on ibl.ai? [Agentic OS](https://ibl.ai/product/agentic-os) is where the agent runs on ibl.ai: it holds the Ironclad MCP connection, the model the agent uses, its instructions and its conversation history. On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network. - [AI agents for Legal](https://ibl.ai/solutions/legal) — what ibl.ai deploys in this sector ### Which ibl.ai agents work with Ironclad data? - [Contract Review](https://ibl.ai/solutions/legal/agent/contract-review-agent) — Legal ### Which ibl.ai platform skills does an Ironclad agent use? - [/iblai-api-agent-mcp](https://ibl.ai/developer/skills/iblai-api-agent-mcp) — MCP connectors for ibl.ai agents, end to end - [/iblai-vibe-agent-mcp](https://ibl.ai/developer/skills/iblai-vibe-agent-mcp) — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,… - [/iblai-api-agent-tool](https://ibl.ai/developer/skills/iblai-api-agent-tool) — Enable or disable an ibl.ai agent's tools via the platform API ## What else should I know before connecting Ironclad to an AI agent? ### Is there an official Ironclad MCP server? Yes. Ironclad publishes [Ironclad MCP server](https://ironcladapp.com/resources/articles/mcp-integrations). You can register it on ibl.ai as an MCP server, or use the SKILL.md when you want the agent to call the Ironclad Public API directly. ### Who can get Ironclad API credentials? An Ironclad customer registers an OAuth client application in Ironclad. The /exports endpoint needs the Security & Data Pro add-on, bought through the Ironclad account team. ### Does Ironclad data leave my infrastructure when an ibl.ai agent uses it? On ibl.ai, you own all the code and the data. Self-hosted in your cloud or data center, the agent, its MCP connections and its conversation logs stay inside your perimeter. Because the platform is model-agnostic, you can point the agent at a model you host, so Ironclad records need not reach a third-party model provider. ### Is the Ironclad agent skill free to use? Yes. The SKILL.md is a free download with no sign-up. It assumes you already have Ironclad credentials, and your agreement with Ironclad still governs how you use its API. ## Which other data sources can an AI agent connect to alongside Ironclad? ### Which other Legal systems have a connector? - [Clio Manage](https://ibl.ai/developer/connectors/clio) — Legal practice management system - [Docusign eSignature](https://ibl.ai/developer/connectors/docusign) — Electronic signature platform - [iManage Work](https://ibl.ai/developer/connectors/imanage) — Legal document and email management system - [LexisNexis](https://ibl.ai/developer/connectors/lexisnexis) — Legal research content and AI API - [NetDocuments](https://ibl.ai/developer/connectors/netdocuments) — Cloud legal document management system - [PACER](https://ibl.ai/developer/connectors/pacer) — U.S. federal court records system - [RelativityOne](https://ibl.ai/developer/connectors/relativity) — E-discovery and legal review platform - [Westlaw](https://ibl.ai/developer/connectors/westlaw) — Legal research platform Every connector, grouped by sector, is on the [connectors hub](https://ibl.ai/developer/connectors).