The Ironclad MCP server exposes Ironclad’s Conversational Search as an MCP tool, allowing AI clients to run read‑only, natural‑language searches over contracts.
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.
The server 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.
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. |
Supported MCP Clients
MCP clients are the apps that talk to the Ironclad MCP server. At this time, only Claude clients are officially supported. Other MCP clients have not been validated and may not behave as expected.
Dynamic Client Registration (DCR) is not supported.
Connect an MCP Client to Ironclad Public API MCP Server
To connect an MCP client to the Ironclad MCP server, you first configure the client with the appropriate Ironclad MCP server URL for the environment you want to access, then complete an OAuth login so Ironclad can authorize requests on behalf of a specific user. Once connected, the client can call Ironclad’s MCP tools in chat to run read-only, permission-aware queries over your contracts.
To learn how to connect an MCP client to Ironclad’s public API MCP server, refer to Connect a Client to Ironclad’s Public API MCP Server.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.
Help Center
Academy
- No relevant resources at this time.