mcp
MCP server for Signb.ee — document signing for AI agents. Gives Claude, Cursor, and Windsurf the ability to send contracts for two-party e-signing with a single tool call. Markdown in, SHA-256 certified signed PDF out. https://signb.ee
Documentation
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 |
|---|---|---|
| `markdown` | ✅ | Document content in markdown format |
| `sender_name` | ✅ | Full name of the sender |
| `sender_email` | ✅ | Email address of the sender |
| `recipient_name` | ✅ | Full name of the recipient |
| `recipient_email` | ✅ | Email address of the recipient |
| `title` | ❌ | Document title (auto-extracted from heading) |
| `expires_in_days` | ❌ | 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 |
|---|---|---|
| `pdf_url` | ✅ | Publicly accessible URL to the PDF |
| `title` | ✅ | Document title |
| `sender_name` | ✅ | Full name of the sender |
| `sender_email` | ✅ | Email address of the sender |
| `recipient_name` | ✅ | Full name of the recipient |
| `recipient_email` | ✅ | Email address of the recipient |
| `expires_in_days` | ❌ | Days until signing link expires (default: 7) |
How It Works
1. You ask your AI to send a document for signing
2. The MCP server calls the Signbee API
3. Signbee converts markdown → PDF, handles the signing ceremony
4. Both parties receive a SHA-256 certified signed copy via email
Get Your API Key
1. Go to signb.ee
2. Create an account
3. Navigate to the Dashboard
4. Copy your API key
Links
- Website: signb.ee
- OpenAPI Spec: signb.ee/openapi.json
- llms.txt: signb.ee/llms.txt
License
MIT
Frequently asked questions
What is mcp?
mcp is MCP server for Signb.ee — document signing for AI agents. Gives Claude, Cursor, and Windsurf the ability to send contracts for two-party e-signing with a single tool call. Markdown in, SHA-256 certified signed PDF out. https://signb.ee
How do I install mcp?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is mcp open source?
Yes — it is hosted on GitHub at https://github.com/signbee/mcp.
Related MCP tools
🔌 Plug-and-play library to enable agents to call MCP and UTCP tools via code execution.
Code research platform for AI agents; find, understand, and prove context across your code and all of GitHub, in a fraction of the tokens. One toolset, MCP or CLI
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
The go-to web for your AI coding agent — local-first search, fetch, crawl & research over MCP. No API keys, no cloud, $0/query. Public beta.
Mobile app automation and verification for AI coding agents. CLI, MCP server, and typed Node.js API for iOS, Android, HarmonyOS, TV, web, macOS, and Linux.
MCP Aggregator, Orchestrator, Middleware, Gateway in one docker
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP