2,500+ MCP servers ready to use
Vinkius

Spellbook Legal AI MCP Server for Google ADK 13 tools — connect in under 2 minutes

Built by Vinkius GDPR 13 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Spellbook Legal AI as an MCP tool provider through the 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="spellbook_legal_ai_agent",
    instruction=(
        "You help users interact with Spellbook Legal AI "
        "using 13 available tools."
    ),
    tools=[mcp_tools],
)
Spellbook Legal AI
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 Spellbook Legal AI MCP Server

Connect to Spellbook Legal AI and bring AI-powered contract drafting, review, and analysis to any AI agent. Trusted by 4,000+ in-house teams and law firms worldwide, Spellbook helps transactional lawyers draft and review contracts faster and more accurately.

Google ADK natively supports Spellbook Legal AI as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 13 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

  • Contract Analysis — AI-powered review of contracts identifying risks, missing clauses, non-standard terms, and issues
  • Clause Suggestions — Get AI-generated clause suggestions based on market standards and best practices
  • Contract Comparison — Compare two contract versions to identify additions, deletions, and modifications
  • Market Comparison — Compare contract terms against 2,000+ market precedents showing pro-buyer, pro-seller, and market-standard positions
  • AI Clause Drafting — Generate AI-drafted clauses based on specified requirements, jurisdiction, and party position
  • Contract Summarization — Generate concise summaries highlighting key terms, obligations, and risks
  • Risk Assessment — Get comprehensive risk assessments with high, medium, and low risk issues and remediations
  • Playbook Compliance — Check contracts against company playbooks to identify deviations from standards
  • Clause Library Search — Search Spellbook's extensive clause library for standard, market-tested clauses
  • Document Management — Upload, list, and search contract documents with filtering by status and type

The Spellbook Legal AI MCP Server exposes 13 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 Spellbook Legal AI to Google ADK via MCP

Follow these steps to integrate the Spellbook Legal AI 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 13 tools from Spellbook Legal AI via MCP

Why Use Google ADK with the Spellbook Legal AI MCP Server

Google ADK provides unique advantages when paired with Spellbook Legal AI 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 Spellbook Legal AI

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 Spellbook Legal AI tools with BigQuery, Vertex AI, and Cloud Functions

Spellbook Legal AI + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Spellbook Legal AI MCP Server delivers measurable value.

01

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

02

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

03

Automated compliance checks: schedule ADK agents to query Spellbook Legal AI 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 Spellbook Legal AI

Spellbook Legal AI MCP Tools for Google ADK (13)

These 13 tools become available when you connect Spellbook Legal AI to Google ADK via MCP:

01

analyze_spellbook_contract

USE WHEN: - User wants to review a contract for risks - User needs to identify issues in a contract - User asks to "analyze this contract" or "review for risks" PARAMETERS: - document_id (REQUIRED): ID of the document to analyze - analysis_type (OPTIONAL): Type of analysis — "full" (default), "risks_only", "clause_check", "market_comparison" EXAMPLES: - "Analyze document 123 for risks" → call with document_id="123" - "Review this contract for issues" → call with document_id="123", analysis_type="full" - "Check clauses in document 456" → call with document_id="456", analysis_type="clause_check" Analyze a contract document for risks, issues, and suggestions

02

check_spellbook_playbook

Check contract compliance against a playbook

03

compare_spellbook_contracts

USE WHEN: - User wants to compare two versions of a contract - User needs to identify changes between drafts - User asks to "compare these contracts" or "show differences" PARAMETERS: - document_id_1 (REQUIRED): ID of the first document - document_id_2 (REQUIRED): ID of the second document - comparison_type (OPTIONAL): Type of comparison — "full" (default), "clauses_only", "risk_comparison" EXAMPLES: - "Compare documents 123 and 456" → call with document_id_1="123", document_id_2="456" - "Show differences between contract versions" → call with document_id_1="123", document_id_2="456", comparison_type="full" Compare two contract versions to identify differences

04

draft_spellbook_clause

USE WHEN: - User needs to draft a new clause for a contract - User wants AI to generate standard clause language - User asks to "draft a limitation of liability clause" or "write an indemnification clause" PARAMETERS: - clause_type (REQUIRED): Type of clause to draft (e.g. "Limitation of Liability", "Indemnification", "Confidentiality") - party_position (OPTIONAL): Which party position to draft for — "neutral" (default), "pro-buyer", "pro-seller", "pro-vendor" - jurisdiction (OPTIONAL): Jurisdiction for the clause (e.g. "New York", "Delaware", "California", "UK") - custom_instructions (OPTIONAL): Additional instructions or requirements for the clause EXAMPLES: - "Draft a limitation of liability clause" → call with clause_type="Limitation of Liability" - "Draft a pro-buyer indemnification clause for New York" → call with clause_type="Indemnification", party_position="pro-buyer", jurisdiction="New York" - "Write a confidentiality clause with custom instructions" → call with clause_type="Confidentiality", custom_instructions="Include data breach notification requirements" Draft a contract clause using Spellbook AI

05

get_spellbook_clause_suggestions

Get AI clause suggestions for a contract document

06

get_spellbook_document

Get detailed information for a specific contract document

07

get_spellbook_market_comparison

Shows pro-buyer, pro-seller, and market-standard positions. Get market comparison data for a specific clause type

08

get_spellbook_risk_assessment

Get a detailed risk assessment for a contract document

09

list_spellbook_documents

Supports filtering by status, document type, and date range. USE WHEN: - User wants to see all their contract documents - User needs to find contracts by status or type - User is exploring their document library - User asks "what contracts do I have" or "list my documents" PARAMETERS: - status (OPTIONAL): Filter by document status (e.g. "Draft", "In Review", "Finalized") - document_type (OPTIONAL): Filter by document type (e.g. "NDA", "MSA", "SOW", "Employment Agreement") - date_from (OPTIONAL): Start date filter (YYYY-MM-DD) - date_to (OPTIONAL): End date filter (YYYY-MM-DD) - page (OPTIONAL): Page number for pagination - page_size (OPTIONAL): Results per page (default: 25, max: 100) EXAMPLES: - "List all my contract documents" → call with no params - "Show contracts in review" → call with status="In Review" - "List NDAs" → call with document_type="NDA" List all contract documents in Spellbook

10

search_spellbook_clause_library

Search the Spellbook clause library for standard clauses

11

search_spellbook_documents

Search contract documents by keyword

12

summarize_spellbook_contract

Generate an AI summary of a contract document

13

upload_spellbook_document

USE WHEN: - User wants to upload a new contract for review - User needs to analyze a contract received from another party - User asks to "upload this contract" or "analyze this document" PARAMETERS: - file_name (REQUIRED): Name of the document file - file_content (REQUIRED): Base64-encoded file content or document text - document_type (OPTIONAL): Type of document (e.g. "NDA", "MSA", "SOW") EXAMPLES: - "Upload this NDA for review" → call with file_name="NDA.pdf", file_content="[base64 content]", document_type="NDA" - "Analyze this MSA contract" → call with file_name="MSA.docx", file_content="[base64 content]", document_type="MSA" Upload a contract document to Spellbook for analysis

Example Prompts for Spellbook Legal AI in Google ADK

Ready-to-use prompts you can give your Google ADK agent to start working with Spellbook Legal AI immediately.

01

"Analyze this NDA for risks and issues."

02

"Draft a pro-buyer limitation of liability clause for Delaware."

03

"Compare the market standard for indemnification clauses."

Troubleshooting Spellbook Legal AI MCP Server with Google ADK

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

01

McpToolset not found

Update: pip install --upgrade google-adk

Spellbook Legal AI + Google ADK FAQ

Common questions about integrating Spellbook Legal AI 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 Spellbook Legal AI to Google ADK

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