Ironclad MCP Server for Claude Code 10 tools — connect in under 2 minutes
Claude Code is Anthropic's agentic CLI for terminal-first development. Add Ironclad as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Ironclad and 2,500+ MCP Servers from a single visual interface.
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add ironclad --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Ironclad MCP Server
Connect your Ironclad account to any AI agent and manage your entire contract lifecycle through natural conversation.
Claude Code registers Ironclad as an MCP server in a single terminal command. Once connected, Claude Code discovers all 10 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Ironclad data drives decisions without human intervention.
What you can do
- Workflows — List active contract workflows, check current step, and track progress through review, approval, and signature
- Launch Contracts — Start new NDAs, MSAs, SOWs, or any contract type from pre-built templates with counterparty details
- Records — Search and browse the executed contract repository with key dates, values, and renewal terms
- Approvals — Check who approved, who is pending, and unblock stuck contracts
- Templates — Browse available contract types ready to launch
- Comments — Review internal discussion threads and negotiation notes on any contract
The Ironclad MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Ironclad to Claude Code via MCP
Follow these steps to integrate the Ironclad MCP Server with Claude Code.
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
Add the MCP Server
Run the command above in your terminal
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
Start using Ironclad
Ask Claude: "Using Ironclad, show me...". 10 tools are ready
Why Use Claude Code with the Ironclad MCP Server
Claude Code provides unique advantages when paired with Ironclad through the Model Context Protocol.
Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
Claude Code runs headlessly, enabling unattended batch processing using Ironclad tools in cron jobs or deployment scripts
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Ironclad + Claude Code Use Cases
Practical scenarios where Claude Code combined with the Ironclad MCP Server delivers measurable value.
CI/CD integration: embed Ironclad tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping
Headless batch processing: schedule Claude Code to query Ironclad nightly and generate reports without human intervention
Shell scripting: pipe Ironclad outputs into other CLI tools for data transformation, filtering, and aggregation
Infrastructure monitoring: run Claude Code in a cron job to query Ironclad status endpoints and alert on anomalies
Ironclad MCP Tools for Claude Code (10)
These 10 tools become available when you connect Ironclad to Claude Code via MCP:
ironclad_get_approvals
Returns each approver with their status (approved/pending/rejected), approval date, and any comments. Essential for tracking where a contract is stuck in the approval process. Use when the user asks "who still needs to approve this contract?" or "why is this contract delayed?" Get the approval status of a specific Ironclad contract workflow — who approved, who is pending, and who rejected
ironclad_get_comments
Returns each comment with author, timestamp, and message. Comments capture internal review discussions, legal feedback, and negotiation notes. Use to review the discussion history of a contract or understand decision context. Get all comments and discussion on an Ironclad contract workflow — internal team communication and negotiation notes
ironclad_get_record
Use for contract lookups, renewal planning, or compliance reviews. Get complete details of an executed Ironclad contract record — all metadata, dates, obligations, and linked documents
ironclad_get_workflow
), current workflow step, assigned reviewers and approvers, counterparty name, related document links, and complete timeline of actions. Use to drill into a specific contract for status updates or details. Get full details of a specific Ironclad contract workflow — current step, all attributes, counterparty info, and timeline
ironclad_launch_workflow
Attributes is a JSON object containing the contract-specific fields defined in the template (e.g., counterparty name, contract value, effective date, jurisdiction). The workflow immediately enters the first step (typically internal review or drafting). Launch a new Ironclad contract workflow from a template — start the process for an NDA, MSA, SOW, or any configured contract type
ironclad_list_records
Returns contract name, counterparty, contract type, key dates (effective, expiration, renewal), total value, and status. Records are the final, executed versions of contracts. Use when the user asks about existing agreements, upcoming renewals, or the contract repository. List executed contract records in Ironclad — fully signed agreements stored in the contract repository with key metadata
ironclad_list_templates
Each template defines: the contract type (NDA, MSA, SOW, amendments, etc.), required attributes/fields, approval chain, and signature requirements. Template IDs are needed to launch new workflows via ironclad_launch_workflow. Use when the user asks "what contract types can we create?" or needs a template ID. List available Ironclad workflow templates — NDA, MSA, SOW, and other pre-configured contract types ready to launch
ironclad_list_webhooks
Webhooks are used to notify external systems when events occur in Ironclad (e.g., workflow launched, contract signed). Returns webhook ID, name, target URL, and events. Use when auditing integrations or checking connectivity. List all configured webhooks in Ironclad — monitor external notifications for workflow events
ironclad_list_workflows
Each workflow represents a contract moving through its lifecycle: drafting → internal review → approval → counterparty negotiation → signature → execution. Returns workflow name, current step/status, creator, counterparty, template used, and dates. Use when the user asks about contracts in progress, pending approvals, or the contract pipeline. List Ironclad contract workflows in progress — NDAs, MSAs, SOWs, and other agreements moving through approval and signature stages
ironclad_search_records
Matches contract names, counterparty names, descriptions, and attribute values. Use when the user asks "find our contract with Acme", "show all NDAs", or needs to locate a specific agreement by keyword. Search Ironclad contract records by keyword — find specific agreements, counterparties, or contract types across the repository
Example Prompts for Ironclad in Claude Code
Ready-to-use prompts you can give your Claude Code agent to start working with Ironclad immediately.
"Show me all contracts pending approval this week"
"Launch an NDA for Acme Corp."
"Search for all active MSAs renewing next month."
Troubleshooting Ironclad MCP Server with Claude Code
Common issues when connecting Ironclad to Claude Code through the Vinkius, and how to resolve them.
Command not found: claude
npm install -g @anthropic-ai/claude-codeConnection timeout
Ironclad + Claude Code FAQ
Common questions about integrating Ironclad MCP Server with Claude Code.
How do I add an MCP server to Claude Code?
claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.Can Claude Code run MCP tools in headless mode?
How do I list all connected MCP servers?
claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.Connect Ironclad with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Ironclad to Claude Code
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.