2,500+ MCP servers ready to use
Vinkius

Ironclad MCP Server for OpenAI Agents SDK 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

The OpenAI Agents SDK enables production-grade agent workflows in Python. Connect Ironclad through Vinkius and your agents gain typed, auto-discovered tools with built-in guardrails. no manual schema definitions required.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MCPServerStreamableHttp(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as mcp_server:

        agent = Agent(
            name="Ironclad Assistant",
            instructions=(
                "You help users interact with Ironclad. "
                "You have access to 10 tools."
            ),
            mcp_servers=[mcp_server],
        )

        result = await Runner.run(
            agent, "List all available tools from Ironclad"
        )
        print(result.final_output)

asyncio.run(main())
Ironclad
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.

The OpenAI Agents SDK auto-discovers all 10 tools from Ironclad through native MCP integration. Build agents with built-in guardrails, tracing, and handoff patterns. chain multiple agents where one queries Ironclad, another analyzes results, and a third generates reports, all orchestrated through Vinkius.

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 OpenAI Agents SDK 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 OpenAI Agents SDK via MCP

Follow these steps to integrate the Ironclad MCP Server with OpenAI Agents SDK.

01

Install the SDK

Run pip install openai-agents in your Python environment

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Run the script

Save the code above and run it: python agent.py

04

Explore tools

The agent will automatically discover 10 tools from Ironclad

Why Use OpenAI Agents SDK with the Ironclad MCP Server

OpenAI Agents SDK provides unique advantages when paired with Ironclad through the Model Context Protocol.

01

Native MCP integration via `MCPServerSse`, pass the URL and the SDK auto-discovers all tools with full type safety

02

Built-in guardrails, tracing, and handoff patterns let you build production-grade agents without reinventing safety infrastructure

03

Lightweight and composable: chain multiple agents and MCP servers in a single pipeline with minimal boilerplate

04

First-party OpenAI support ensures optimal compatibility with GPT models for tool calling and structured output

Ironclad + OpenAI Agents SDK Use Cases

Practical scenarios where OpenAI Agents SDK combined with the Ironclad MCP Server delivers measurable value.

01

Automated workflows: build agents that query Ironclad, process the data, and trigger follow-up actions autonomously

02

Multi-agent orchestration: create specialist agents. one queries Ironclad, another analyzes results, a third generates reports

03

Data enrichment pipelines: stream data through Ironclad tools and transform it with OpenAI models in a single async loop

04

Customer support bots: agents query Ironclad to resolve tickets, look up records, and update statuses without human intervention

Ironclad MCP Tools for OpenAI Agents SDK (10)

These 10 tools become available when you connect Ironclad to OpenAI Agents SDK via MCP:

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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 OpenAI Agents SDK

Ready-to-use prompts you can give your OpenAI Agents SDK agent to start working with Ironclad immediately.

01

"Show me all contracts pending approval this week"

02

"Launch an NDA for Acme Corp."

03

"Search for all active MSAs renewing next month."

Troubleshooting Ironclad MCP Server with OpenAI Agents SDK

Common issues when connecting Ironclad to OpenAI Agents SDK through the Vinkius, and how to resolve them.

01

MCPServerStreamableHttp not found

Ensure you have the latest version: pip install --upgrade openai-agents
02

Agent not calling tools

Make sure your prompt explicitly references the task the tools can help with.

Ironclad + OpenAI Agents SDK FAQ

Common questions about integrating Ironclad MCP Server with OpenAI Agents SDK.

01

How does the OpenAI Agents SDK connect to MCP?

Use MCPServerSse(url=...) to create a server connection. The SDK auto-discovers all tools and makes them available to your agent with full type information.
02

Can I use multiple MCP servers in one agent?

Yes. Pass a list of MCPServerSse instances to the agent constructor. The agent can use tools from all connected servers within a single run.
03

Does the SDK support streaming responses?

Yes. The SDK supports SSE and Streamable HTTP transports, both of which work natively with Vinkius.

Connect Ironclad to OpenAI Agents SDK

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.