How do I get started with Ironclad?

Subscribe, then enter your Ironclad API token (from **Company Settings → API → Access Tokens**). Your AI agent connects instantly to your workspace. No code, no SDK, no webhooks — just connect and start managing contracts through conversation.

Can my AI agent launch a new contract for a counterparty?

Yes. Tell your agent to launch a contract (e.g., "start an NDA for Acme Corp") and it selects the right template, fills in counterparty details, contract value, and effective dates. The workflow enters internal review immediately — your legal team sees it in their queue within seconds.

How do I find out why a contract is stuck in approval?

Ask your agent "who still needs to approve the Acme MSA?" and it shows every approver with their status — approved, pending, or rejected — plus any comments they left. You see exactly who is blocking the contract and can follow up directly, all without opening Ironclad.

Can I manage complex contract portfolios with multiple contract types?

Absolutely. Browse all your workflow templates (NDAs, MSAs, SOWs, amendments, renewals), search across the entire executed contract repository by counterparty or keyword, and track renewal dates — perfect for legal departments, procurement teams, and enterprises managing hundreds of active agreements.

Ironclad MCP Server for Mastra AI 10 tools — connect in under 2 minutes

Name: Ironclad
Availability: InStock
Author: Vinkius

docs.mastra.ai/docs/agents/mcp-tools

Built by Vinkius GDPR 10 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Ironclad through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

typescript

import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "ironclad": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Ironclad Agent",
    instructions:
      "You help users interact with Ironclad " +
      "using 10 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Ironclad?"
  );
  console.log(result.text);
}

main();

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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.

Mastra's agent abstraction provides a clean separation between LLM logic and Ironclad tool infrastructure. Connect 10 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Ironclad MCP Server with Mastra AI.

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.ts and run with npx tsx agent.ts

Explore tools

Mastra discovers 10 tools from Ironclad via MCP

Why Use Mastra AI with the Ironclad MCP Server

Mastra AI provides unique advantages when paired with Ironclad through the Model Context Protocol.

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Ironclad without touching business code

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

TypeScript-native: full type inference for every Ironclad tool response with IDE autocomplete and compile-time checks

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

Ironclad + Mastra AI Use Cases

Practical scenarios where Mastra AI combined with the Ironclad MCP Server delivers measurable value.

Automated workflows: build multi-step agents that query Ironclad, process results, and trigger downstream actions in a typed pipeline

SaaS integrations: embed Ironclad as a first-class tool in your product's AI features with Mastra's clean agent API

Background jobs: schedule Mastra agents to query Ironclad on a cron and store results in your database automatically

Multi-agent systems: create specialist agents that collaborate using Ironclad tools alongside other MCP servers

Ironclad MCP Tools for Mastra AI (10)

These 10 tools become available when you connect Ironclad to Mastra AI 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