Ironclad MCP Server for CrewAI 10 tools — connect in under 2 minutes
Connect your CrewAI agents to Ironclad through Vinkius, pass the Edge URL in the `mcps` parameter and every Ironclad tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Ironclad Specialist",
goal="Help users interact with Ironclad effectively",
backstory=(
"You are an expert at leveraging Ironclad tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Ironclad "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 10 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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.
When paired with CrewAI, Ironclad becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Ironclad tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
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 CrewAI 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 CrewAI via MCP
Follow these steps to integrate the Ironclad MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 10 tools from Ironclad
Why Use CrewAI with the Ironclad MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Ironclad through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Ironclad + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Ironclad MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Ironclad for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Ironclad, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Ironclad tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Ironclad against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Ironclad MCP Tools for CrewAI (10)
These 10 tools become available when you connect Ironclad to CrewAI 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 CrewAI
Ready-to-use prompts you can give your CrewAI 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 CrewAI
Common issues when connecting Ironclad to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Ironclad + CrewAI FAQ
Common questions about integrating Ironclad MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.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 CrewAI
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.