How to Add E-Signing to Claude, Cursor, and Windsurf in 2 Minutes

What the MCP server does

Most MCP servers connect your AI to databases, file systems, or search engines. This one lets your AI send legally binding documents for signature.

Signbee's MCP server gives Claude CoWork, Cursor, and Windsurf two new tools:

send_document — Takes markdown content and sends it as a formatted PDF for two-party e-signing. You provide the sender name, sender email, recipient name, and recipient email. Signbee generates the PDF, verifies both parties via email OTP, and delivers a signed copy with a tamper-proof SHA-256 certificate.

send_document_pdf — Same signing flow, but instead of markdown you pass a URL to an existing PDF. Useful when you've already got a formatted contract, proposal, or agreement and just need the signing ceremony handled.

Both tools work with or without an API key. Without one, the sender gets an OTP email to verify their identity. With one, documents are sent instantly — no verification step for the sender.

Setup: Claude CoWork

Claude CoWork uses “Connectors” — which are MCP servers under the hood. For built-in integrations like Google Drive or Slack, you enable them directly in settings. For custom MCP servers like Signbee, you add them to the Claude Desktop configuration file.

Step 1: Open your Claude Desktop config file.

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Step 2: Add the Signbee MCP server:

{
  "mcpServers": {
    "signbee": {
      "command": "npx",
      "args": ["-y", "signbee-mcp"],
      "env": {
        "SIGNBEE_API_KEY": "your-api-key-from-signb.ee/dashboard"
      }
    }
  }
}

Step 3: Restart Claude Desktop. The Signbee tools will appear in CoWork's tool list.

Try it: Open CoWork and type: “Send a mutual NDA between me (michael@company.com) and Sarah Chen (sarah@acme.com)”

Claude will draft the NDA in markdown, call the send_document tool, and both parties will receive signing emails within seconds.

Setup: Cursor

Cursor has native MCP support built into the editor. You can configure it through the settings UI or by editing the config file directly.

Option A — Via Settings UI:

1. Open Command Palette (Cmd + Shift + P)
2. Navigate to Settings → Features → MCP
3. Click “+ Add New MCP Server”
4. Enter: Name: signbee, Type: stdio, Command: npx, Args: -y signbee-mcp
5. Add environment variable: SIGNBEE_API_KEY = your key

Option B — Via config file:

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-specific):

{
  "signbee": {
    "command": "npx",
    "args": ["-y", "signbee-mcp"],
    "env": {
      "SIGNBEE_API_KEY": "your-api-key"
    }
  }
}

Once connected, ask Cursor's agent: “Send this README as a signed agreement to the client at client@example.com”

Setup: Windsurf

Windsurf connects MCP servers through its Cascade agent panel.

Option A — Via Cascade UI:

1. Open the Cascade panel
2. Click the MCPs icon (top-right corner)
3. If Signbee appears in the marketplace, click Install
4. If not, click Manage Plugins → View raw config

Option B — Edit the config file directly:

• macOS/Linux: ~/.codeium/windsurf/mcp_config.json
• Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

{
  "mcpServers": {
    "signbee": {
      "command": "npx",
      "args": ["-y", "signbee-mcp"],
      "env": {
        "SIGNBEE_API_KEY": "your-api-key"
      }
    }
  }
}

Save and refresh Windsurf. Cascade will pick up the new tools automatically.

What happens after you send

Once your agent calls the tool, Signbee takes over the entire signing ceremony:

1. Document generated — Markdown is converted to a clean PDF, or your provided PDF is downloaded and prepared for signing
2. Sender verified — If using an API key, this is instant. Otherwise, the sender gets a 6-digit OTP via email
3. Recipient notified — An email is sent with a secure, time-limited signing link
4. Recipient signs — They review the document, type their name, and sign with an animated handwriting signature
5. Certificate appended — A final page is added to the PDF with timestamps, IP addresses, verification methods, and a SHA-256 hash of the entire document
6. Both parties receive the signed PDF — Delivered via email with the certificate proving the document hasn't been tampered with

The entire flow typically takes under 60 seconds from the moment the agent calls the tool to both parties having a certified copy.

Three things most people don't realise

1. You don't need an API key to start. The MCP server works without one. The sender verifies via email OTP instead. This means you can try it right now — no account, no dashboard, no credit card.

2. The agent can draft the contract for you. You don't need to write the markdown yourself. Ask Claude to “draft a freelance design contract and send it to jane@studio.com” — it will write the contract, format it in markdown, and send it through Signbee in a single interaction.

3. It works with existing PDFs too. If you have a contract template hosted somewhere — Google Drive public link, S3 URL, any publicly accessible URL — you can pass the pdf_url parameter instead of markdown. The agent uses the send_document_pdf tool and your existing design is preserved exactly as-is.

API key vs. OTP: when to use each

For day-to-day use in CoWork or Cursor, the OTP flow is fine — you verify once per document via email. For automated agents running unsupervised, you'll want the API key so documents send instantly without waiting for human verification.

Get your API key

1. Go to signb.ee
2. Create a free account
3. Open the Dashboard
4. Copy your API key from the API Keys section

Free tier gives you 5 documents per month — enough to properly test the integration and send real contracts.

What's next

We're working on adding the Signbee MCP server to the official MCP registries and marketplaces. Soon you'll be able to install it directly from Windsurf's marketplace and Cursor's MCP directory without editing config files.

We're also exploring deeper integration with Claude CoWork's Connectors system — the goal is for Signbee to appear as a first-class connector alongside Google Drive, GitHub, and Slack.

If you run into any issues, the full documentation is at signb.ee/docs and the MCP server source is on GitHub.