Sign Documents Directly from Claude | Zignature + Anthropic MCP

Q: How do I connect Claude to Zignature for document signing?

You can connect Claude to Zignature using two methods: for claude.ai web, use the Remote MCP integration by pasting https://app.zignature.io/mcp into your settings. For Claude Desktop, add the Zignature MCP server configuration to your claude_desktop_config.json file.

Q: Do I need an API key to use Claude with Zignature?

For the claude.ai web integration, you do not need an API key as it uses OAuth. For Claude Desktop, you will need an API token from the Zignature Developer Portal.

Q: What documents can Claude send via Zignature?

Claude can send any document template you have set up in Zignature, including NDAs, MSAs, SOWs, and offer letters. You can also tell Claude to draft new documents based on your templates.

Q: Is the Claude + Zignature integration secure?

Yes. The integration uses the Model Context Protocol (MCP) and follows industry-standard security practices. The web integration uses OAuth 2.0 + PKCE, ensuring your credentials are never exposed to the AI.

Q: How is this different from using the Zignature API directly?

MCP allows Claude to understand and use Zignature's tools in natural language. Instead of writing code to call the API, you can simply tell Claude what you want to do, and it handles the tool calls for you.

Choose Your Connection Method

Get set up in seconds on the web or in your desktop app.

claude.ai Web (Remote MCP)

Best for everyday use. Connects directly to the Anthropic web interface with zero local configuration.

1

Go to claude.ai → Settings → Integrations
2

Click "Add custom integration"
3

Paste: https://app.zignature.io/mcp
4

Log in to Zignature and approve — done!

Note: Claude auto-discovers all 57 tools via OAuth. No API key needed.

Claude Desktop

For power users and developers. Runs locally on your machine for maximum performance.

1

Get API key from Developer Portal
2

Edit ~/Library/Application Support/Claude/claude_desktop_config.json

3

Add the JSON config block:

{
  "mcpServers": {
    "zignature": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch"],
      "env": {
        "MCP_SERVER_URL": "https://app.zignature.io/mcp",
        "MCP_AUTH_HEADER": "X-Auth-Token YOUR_API_KEY"
      }
    }
  }
}

4

Restart Claude Desktop

What You Can Do with Claude

57 powerful tools at your fingertips.

Send Documents

Track Status

Manage Templates

Bulk Send

Download PDFs

Manage Team

CLM

Deal Desk

Webhooks

Account Settings

See It in Action

Natural language document management with Claude.

Claude Conversation

U

Send the Q2 MSA to john@acme.com. He's the client, I'm the account owner.

C

I'll send your Q2 MSA template now.

Document sent to john@acme.com

Signing link: https://sign.zignature.io/d/q2msa_9kx2

I'll let you know when John opens or signs it.

U

What contracts are still waiting on signatures?

C

You have 3 documents awaiting signature:

• Q2 MSA — John Smith (Acme) — sent 2 days ago
• Developer NDA — Sarah Chen — sent 5 days ago
• Vendor Agreement — Bob Wilson — sent 1 day ago

Want me to send reminders to any of them?

U

Send a reminder to Sarah

C

Reminder sent to sarah@example.com for the Developer NDA.

Why Claude + Zignature?

Natural Language Contract Management

Stop navigating complex menus. Simply ask Claude to list your contracts, send reminders, or check a document's audit trail.

Context-Aware Signing

Claude understands the context of your conversation. If you're discussing a deal, it knows exactly when it's time to send the contract.

Works in Projects

Give Claude persistent access to your signing workflow within specific Projects, allowing it to maintain state and history across sessions.

Frequently Asked Questions

How do I connect Claude to Zignature for document signing?

You can connect Claude to Zignature using two methods: for claude.ai web, use the Remote MCP integration by pasting https://app.zignature.io/mcp into your settings. For Claude Desktop, add the Zignature MCP server configuration to your claude_desktop_config.json file.

Does Zignature support claude.ai web (Remote MCP)?

Yes, Zignature fully supports Remote MCP on claude.ai web. This allows for a zero-config, 1-click connection using OAuth for authentication, making it incredibly easy to start signing documents directly in your browser.

Do I need an API key to use Claude with Zignature?

For the claude.ai web integration, you do not need an API key as it uses OAuth for secure authentication. For Claude Desktop, you will need to generate an API token from the Zignature Developer Portal to authenticate your local MCP server instance.

What documents can Claude send via Zignature?

Claude can send any document template you have set up in your Zignature account, including NDAs, Master Service Agreements (MSAs), Statements of Work (SOWs), and more. You can also tell Claude to draft new documents based on your templates or previous conversations.

Is the Claude + Zignature integration secure?

Absolutely. The integration built on the Model Context Protocol (MCP) follows enterprise-grade security standards. The web integration uses OAuth 2.0 with PKCE, ensuring that your Zignature credentials are never shared with Anthropic or the AI model itself.

How is this different from using the Zignature API directly?

While the API requires writing code (Python, JS, etc.) to automate tasks, the MCP integration allows Claude to "understand" your document workflow. You can communicate in natural language, and Claude intelligently decides which Zignature tools to call, handling all the technical complexity for you.