2,500+ MCP servers ready to use
Vinkius

Ironclad MCP Server for Google ADK 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Ironclad as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Vinkius supports streamable HTTP and SSE.

python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="ironclad_agent",
    instruction=(
        "You help users interact with Ironclad "
        "using 10 available tools."
    ),
    tools=[mcp_tools],
)
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.

Google ADK natively supports Ironclad as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 10 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

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 Google ADK 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 Google ADK via MCP

Follow these steps to integrate the Ironclad MCP Server with Google ADK.

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 10 tools from Ironclad via MCP

Why Use Google ADK with the Ironclad MCP Server

Google ADK provides unique advantages when paired with Ironclad through the Model Context Protocol.

01

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Ironclad

03

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

04

Seamless integration with Google Cloud services means you can combine Ironclad tools with BigQuery, Vertex AI, and Cloud Functions

Ironclad + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Ironclad MCP Server delivers measurable value.

01

Enterprise data agents: ADK agents query Ironclad and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Ironclad tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Ironclad regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Ironclad

Ironclad MCP Tools for Google ADK (10)

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

Ready-to-use prompts you can give your Google ADK 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 Google ADK

Common issues when connecting Ironclad to Google ADK through the Vinkius, and how to resolve them.

01

McpToolset not found

Update: pip install --upgrade google-adk

Ironclad + Google ADK FAQ

Common questions about integrating Ironclad MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Connect Ironclad to Google ADK

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