Today we're excited to announce that Zignature now supports the Model Context Protocol (MCP) — an open standard that lets AI assistants like Claude, Cursor, ChatGPT, and VS Code Copilot interact directly with your document signing workflows. This makes Zignature the first e-signature platform to offer native MCP integration.
What Is MCP?
The Model Context Protocol is an open standard originally developed by Anthropic that provides a universal way for AI applications to connect with external tools and data sources. Think of it as a USB-C port for AI — one standard protocol that works with any compatible AI assistant.
Instead of building separate integrations for every AI tool, MCP provides a single server endpoint that any MCP-compatible client can connect to. This means that as new AI tools adopt the protocol, they'll automatically work with Zignature.
What Can You Do with Zignature + MCP?
Once connected, your AI assistant can perform a wide range of document operations on your behalf:
- Send documents for signature — Tell your AI assistant: "Send the NDA template to jane@example.com for signature" and it handles everything
- Check document status — Ask "What's the status of the contract I sent to Acme Corp?" and get real-time updates
- List and search templates — Browse your template library with natural language queries
- Get smart template suggestions — Describe what you need and get AI-powered recommendations from your existing templates
- Download signed documents — Retrieve completed documents and audit trails
- Void pending documents — Cancel documents that are no longer needed
Real-World Use Cases
For Sales Teams
Imagine closing a deal and telling your AI assistant: "Send our standard enterprise agreement to the three stakeholders at Acme Corp." The AI selects the right template, fills in the recipient details, and sends it — all without leaving your current workflow.
For Legal Teams
Ask your AI assistant to "Show me all unsigned contracts from this month" or "What NDAs are still pending?" to get instant visibility into your document pipeline without switching to a dashboard.
For Developers
Build AI-powered document workflows in your IDE. From Cursor or VS Code, you can send test documents, check integration statuses, and manage templates — all through natural language commands.
How to Set It Up
Getting started takes less than two minutes:
- Get your API key from the Zignature Developer Portal under API Keys
- Add the MCP server to your AI tool's configuration
- Start using natural language to manage your documents
For Claude Desktop, add this to your configuration file:
{
"mcpServers": {
"zignature": {
"url": "https://app.zignature.io/mcp",
"headers": {
"X-Auth-Token": "YOUR_API_KEY"
}
}
}
}For Cursor, the setup is similar — just add the server URL and your API key in the MCP settings panel.
Nine Powerful Tools at Your Fingertips
The Zignature MCP server exposes nine tools that cover the full document lifecycle:
- list_templates — Search and browse your template library
- get_template — Get detailed information about any template
- send_document — Send a document for signature with full control over recipients and options
- list_documents — View submissions filtered by status or template
- get_document_status — Get real-time status of any submission
- void_document — Cancel a pending document
- download_document — Get download URLs for signed documents
- get_audit_trail — Access the complete audit trail for compliance
- suggest_template — Get AI-powered template recommendations based on natural language descriptions
Why MCP Matters for E-Signatures
The document signing industry has been slow to embrace AI integration. While competitors like DocuSign offer basic API access, none provide the seamless AI assistant experience that MCP enables. With Zignature's MCP support, you can:
- Eliminate context switching — Stay in your AI assistant while managing documents
- Reduce manual work — Let AI handle the repetitive parts of document workflows
- Future-proof your stack — As new AI tools adopt MCP, they'll work with Zignature automatically
- Maintain security — All operations use your existing API key with the same permissions and audit logging
Security and Compliance
MCP requests are authenticated using the same API keys you already use, with full audit logging of every operation. All existing security controls — including IP allowlists, role-based access, and retention policies — apply to MCP operations. Your documents and data never leave Zignature's infrastructure.
Get Started Today
MCP support is available now for all Zignature plans. Visit the MCP documentation in our Developer Portal to get started, or head to API Keys to generate your token.
We're just getting started with AI integration. Stay tuned for more tools and capabilities in the coming months.