Ironclad Contracts logo

Ironclad Contracts

Plain language search for faster contract answers

Official docs

About Ironclad Contracts

Ironclad Contracts provides plain-language search for contract answers. Its connector brings contract repository context into assistant workflows so legal and business teams can find agreement terms, obligations, and related records faster.

Connection details

https://mcp.na1.ironcladapp.com/mcp
Transport
Streamable HTTP
Authentication
OAuth

Setup

claude mcp add ironclad-contracts --transport http https://mcp.na1.ironcladapp.com/mcp

Frequently asked questions

What is the Ironclad Contracts remote MCP server?

The Ironclad Contracts remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.na1.ironcladapp.com/mcp, so AI assistants can connect to it without installing or running anything locally. Ironclad Contracts provides plain-language search for contract answers. Its connector brings contract repository context into assistant workflows so legal and business teams can find agreement terms, obligations, and related records faster.

How do I connect to the Ironclad Contracts MCP server?

Add the endpoint https://mcp.na1.ironcladapp.com/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the Ironclad Contracts MCP server require authentication?

Yes. Ironclad Contracts uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the Ironclad Contracts MCP server use?

Ironclad Contracts exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.

More remote MCP servers