signbee-mcp
Signbee MCP Server enables AI agents to send documents for legally-binding two-party e-signing from MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.
Send a markdown document for e-signing (
send_document): Provide markdown content with sender/recipient details; Signbee auto-converts it to a professional PDF and initiates the signing workflow. The document title can be auto-extracted from the first heading if not provided.Send an existing PDF for e-signing (
send_document_pdf): Provide a publicly accessible PDF URL along with sender/recipient details to initiate signing.Automated signing ceremony: Handles the full flow — emailing the recipient a signing link and delivering a SHA-256 certified signed copy to both parties upon completion.
Configurable expiry: Set signing link validity from 1–30 days (default: 7).
Optional API key authentication: Without an API key, the sender verifies via email OTP; with one, documents are sent instantly.
Enables the conversion of Markdown document content into professional, SHA-256 certified PDFs for two-party e-signing, including automatic document title extraction from Markdown headings.
Signbee MCP Server
Document signing for AI agents — as an MCP tool.
Send, sign, and verify documents with a single tool call. Works with Claude, Cursor, Windsurf, and any MCP-compatible client.
Quick Setup
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"signbee": {
"command": "npx",
"args": ["-y", "signbee-mcp"],
"env": {
"SIGNBEE_API_KEY": "your-api-key-from-signb.ee/dashboard"
}
}
}
}Cursor / Windsurf
Add to your MCP settings:
{
"signbee": {
"command": "npx",
"args": ["-y", "signbee-mcp"],
"env": {
"SIGNBEE_API_KEY": "your-api-key"
}
}
}Note: The API key is optional. Without it, the sender verifies via email OTP. With it, documents are sent instantly.
Tools
send_document
Send a markdown document for two-party e-signing.
Parameters:
Parameter | Required | Description |
| ✅ | Document content in markdown format |
| ✅ | Full name of the sender |
| ✅ | Email address of the sender |
| ✅ | Full name of the recipient |
| ✅ | Email address of the recipient |
| ❌ | Document title (auto-extracted from heading) |
| ❌ | Days until signing link expires (default: 7) |
Example prompt: "Send an NDA to bob@acme.com from alice@company.com"
send_document_pdf
Send an existing PDF for two-party e-signing.
Parameters:
Parameter | Required | Description |
| ✅ | Publicly accessible URL to the PDF |
| ✅ | Document title |
| ✅ | Full name of the sender |
| ✅ | Email address of the sender |
| ✅ | Full name of the recipient |
| ✅ | Email address of the recipient |
| ❌ | Days until signing link expires (default: 7) |
How It Works
You ask your AI to send a document for signing
The MCP server calls the Signbee API
Signbee converts markdown → PDF, handles the signing ceremony
Both parties receive a SHA-256 certified signed copy via email
Get Your API Key
Go to signb.ee
Create an account
Navigate to the Dashboard
Copy your API key
Links
Website: signb.ee
OpenAPI Spec: signb.ee/openapi.json
llms.txt: signb.ee/llms.txt
License
MIT
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/signbee/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server