Ironclad MCP Server

Ironclad's MCP server is a remote, provider-hosted endpoint that connects MCP-compatible AI clients to an Ironclad workspace. It exposes Ironclad's Conversational Search, the same AI engine behind the Dashboard search experience, as an MCP tool. Once authorized, an agent can answer questions like "NDAs governed by California law that expire in the next 12 months" by searching executed contracts, workflows, and records that the signed-in user has permission to view.

The server is read-only and permission-aware: every request is scoped to the authenticated Ironclad user, so the agent can only see what that user could see in the product. Authentication is performed via an OAuth login flow against Ironclad, so no long-lived API keys are stored in the client. Ironclad currently lists Claude as the only officially supported MCP client; other clients may work but are not validated.

The official server is featured in Anthropic's Claude Connectors Directory and the claude-for-legal commercial-legal plugin. If you need write actions (launching workflows, updating records, managing approvals or signatures), you will likely need a third-party MCP wrapper around Ironclad's Public API (for example Zapier, Pipedream, Gumloop, or Vinkius), since the official server is currently scoped to conversational search.

Tools

Prerequisites

• An Ironclad workspace and a user account with permissions to access contracts.
• An MCP client that supports remote MCP servers with OAuth (Claude Desktop, Claude.ai, or Claude Code are the officially supported clients).
• Your Ironclad admin may need to enable the MCP connector for your workspace.

Add the connector in Claude

In Claude Desktop or Claude.ai, go to Settings → Connectors → Add custom connector and use the Ironclad MCP server URL for your environment:

https://mcp.ironcladapp.com/mcp

Complete the OAuth login when prompted so Ironclad can authorize requests on behalf of your user.

Claude Code / generic MCP client config

For clients that accept a JSON config block for remote MCP servers:

{
  "mcpServers": {
    "ironclad": {
      "url": "https://mcp.ironcladapp.com/mcp",
      "transport": "http"
    }
  }
}

The client will open a browser window for the Ironclad OAuth flow on first use. No API token needs to be pasted into the config.

Notes

• All calls are read-only and respect the signed-in user's permissions in Ironclad.
• Only Claude clients are officially validated; other MCP clients may not behave as expected.
• For write operations such as launching workflows or updating records, see the alternatives below.

• Ask Claude "Which active NDAs are governed by California law and expire in the next 12 months?" and get a filtered list pulled directly from Ironclad.
• Run quick due-diligence lookups during a deal review, for example "Find all MSAs with Acme Corp and summarize the termination clauses."
• Locate obligations and renewal dates across the executed contract repository without leaving the chat client.
• Help legal ops triage requests by searching for in-flight workflows by counterparty, contract type, or owner.
• Pair with Anthropic's claude-for-legal commercial-legal plugin to combine Ironclad search with other legal data sources (DocuSign, iManage, etc.).

• "Find all NDAs governed by California law that expire in the next 12 months."
• "Summarize the indemnification clauses in our executed MSAs with Fortune 500 customers."
• "Which contracts with Acme Corp are currently active and what are their renewal dates?"
• "List executed SOWs over $500k signed in the last quarter and show the counterparties."
• "Search our contract repository for any agreements that include exclusivity language."

• Official, provider-hosted server with no infrastructure to run and no API keys to rotate.
• Permission-aware: results are scoped to what the authenticated Ironclad user is allowed to see.
• Uses Ironclad's native semantic search engine, so it understands clause and metadata filters in plain English.
• Listed in Anthropic's Claude Connectors Directory and bundled into the claude-for-legal commercial-legal plugin.

• Read-only: the official server does not support launching workflows, updating records, or managing approvals or signatures.
• Only Claude clients are officially supported at this time; other MCP clients are not validated.
• Requires an Ironclad workspace and may need admin enablement, so it is not usable without a paid Ironclad subscription.

• Zapier MCP for Ironclad (https://zapier.com/mcp/ironclad) wraps Ironclad's Public API with write actions like Create Record, Update Workflow, and Create Workflow Comment.
• Pipedream MCP for Ironclad (https://mcp.pipedream.com/app/ironclad) provides a dynamic toolset over the Ironclad API with managed auth.
• Gumloop MCP for Ironclad (https://docs.gumloop.com/nodes/mcp/ironclad) exposes ~15 tools covering workflows, approvals, signatures, comments, and record metadata.