2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 13 Tools SDK

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

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: {
      "spellbook-legal-ai": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

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

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

main();
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.

Mastra's agent abstraction provides a clean separation between LLM logic and Spellbook Legal AI tool infrastructure. Connect 13 tools through the 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

  • 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 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 Spellbook Legal AI to Mastra AI via MCP

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

01

Install dependencies

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

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

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

04

Explore tools

Mastra discovers 13 tools from Spellbook Legal AI via MCP

Why Use Mastra AI with the Spellbook Legal AI MCP Server

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

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Spellbook Legal AI without touching business code

02

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

03

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

04

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

Spellbook Legal AI + Mastra AI Use Cases

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

01

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

02

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

03

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

04

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

Spellbook Legal AI MCP Tools for Mastra AI (13)

These 13 tools become available when you connect Spellbook Legal AI to Mastra AI 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 Mastra AI

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

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Spellbook Legal AI + Mastra AI FAQ

Common questions about integrating Spellbook Legal AI MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Spellbook Legal AI to Mastra AI

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