Summary
This article walks you through how to connect an MCP Client to the Ironclad MCP Server.
Note: MCP stands for Model Context Protocol. It’s an open standard that lets AI models connect securely to external tools and data sources through a single, shared interface—basically a “universal port” so many different AI clients can call the same tools without custom integrations.
Permissions
| Features | API, Search |
| Permissions | Your use of the MCP server complies with whatever user and group permissions are associated with your Ironclad user account. |
MCP Server URLs
The Ironclad MCP server URL is the address your AI client (such as Claude) uses to connect to Ironclad’s MCP server so it can:
- discover the Ironclad MCP tools (like Conversational Search), and
- send authenticated, permission-aware MCP requests to search/read Ironclad contract data from within the AI chat experience.
Refer to the URLs below to define which Ironclad environment you want to search:
| Ironclad Environment | Server URL |
|---|---|
| NA1 production | https://mcp.na1.ironcladapp.com/mcp |
| EU1 production | https://mcp.eu1.ironcladapp.com/mcp |
| Demo / sandbox | https://mcp.demo.ironcladapp.com/mcp |
Tools
Conversational Search
conversational_search lets you run natural-language searches using the same AI engine as Ironclad’s Dashboard Conversational Search, understands complex semantic filters for prompts like “NDAs governed by California law that expire in the next 12 months,” and returns only the results the signed-in Ironclad user is authorized to access. It is read-only, supporting search only and never creating, editing, or deleting data.
Release: The following functionality will be live on July 23rd. To learn more about the features included in our July release, refer to What's New in Ironclad: July 2026.
Manage Obligations
create_obligation, get_obligation, list_obligations, list_obligation_types, and update_obligation — let clients create, read, list, and update contractual obligations (type, name, description, status, owner) tied to Ironclad records. This requires the Obligations add-on, and access follows the same record based permissions as the product.
MCP Tool Availability
A tool can be enabled but not yet usable. When viewing tools in MCP, you may see tools that are enabled but not usable. A tool is usable only if both are true: (a) your current MCP session granted the scopes that tool requires, and (b) your MCP client supports that tool. A tool may appear in tools/list because it is enabled for your company but still not work if your current session did not grant the required scopes (reconnect to fix), or your MCP client does not support that tool the same way another client does (e.g., Slack vs. Claude may support different tools).
Reconnect before using new tools. You must reconnect to the MCP server before using any new tool you have not used before.
Connect Claude.ai to Ironclad MCP Server
- Add an HTTP MCP server/connector in your AI client. For the server URL, paste the Ironclad MCP Server URL to define which Ironclad environment you want to search.
-
Authenticate with Ironclad.
- Click Connect (or equivalent) to trigger the OAuth login flow.
- Log in to Ironclad and authorize the requested scopes (including conversational search + read scopes for workflows/records).
- Use the tool in chat. For example, “use the Ironclad MCP to find all active NDAs expiring in the next 90 days”.
Connect Claude Code to Ironclad MCP Server
-
Add the Ironclad MCP server to your client. For the server URL, paste the Ironclad MCP Server URL to define which Ironclad environment you want to search. For example:
claude mcp add --transport http <NAME> <URL> - Complete OAuth in your browser. The client will open a browser window pointing at Ironclad’s OAuth server. Log in and approve the requested scopes.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.
Help Center
Academy
- No relevant resources at this time.