
Signbee — Document Signing for AI Agents
@signbee
About Signbee — Document Signing for AI Agents
Send, sign, and verify documents with a single tool call. Converts markdown to PDF, handles two-party signing via email, and delivers SHA-256 certified signed copies. No SDK, no browser — just npx signbee-mcp.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"signbee": {
"command": "npx",
"args": [
"-y",
"signbee-mcp"
],
"env": {
"SIGNBEE_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Tools
2Send a document for two-party e-signing. Converts markdown to PDF, verifies the sender, emails the recipient a signing link, and delivers a SHA-256 certified signed copy to both parties.
Send an existing PDF document for two-party e-signing. Use this when you already have a PDF URL instead of markdown content.
Overview
What is Signbee — Document Signing for AI Agents?
Signbee — Document Signing for AI Agents is an MCP server that enables AI agents to send documents for two-party e-signing. It converts markdown to professional PDFs, coordinates signatures via email, and delivers SHA-256 certified copies.
How to use Signbee — Document Signing for AI Agents?
Install from npm (signbee-mcp) and configure as an MCP tool. Invoke either the send_document tool (with parameters: markdown, sender_name, sender_email, recipient_name, recipient_email, plus optional title and expires_in_days) or the send_document_pdf tool (with parameters: pdf_url, title, sender_name, sender_email, recipient_name, recipient_email, plus optional expires_in_days).
Key features of Signbee — Document Signing for AI Agents
- Send markdown documents for two-party e-signing as a tool
- Automatic markdown-to-PDF conversion with professional layout
- Email-based signature workflow for both parties
- SHA-256 certified copy delivered upon completion
- Support for sending existing PDFs directly
- Optional document title and expiration duration
Use cases of Signbee — Document Signing for AI Agents
- AI agents initiating contract signing without human intervention
- Automating two-party agreement workflows from markdown content
- Sending pre-existing PDFs for e-signature collection
- Triggering document signing as part of a broader MCP toolchain
FAQ from Signbee — Document Signing for AI Agents
What exactly does this server do?
It provides two MCP tools — send_document and send_document_pdf — that let an AI agent send a markdown document or an existing PDF for two-party e-signing, with signatures collected via email and a SHA-256 certified copy delivered.
What dependencies or runtime are required?
The server is available as an npm package (signbee-mcp). It requires an MCP-compatible client to invoke the tools; no additional signing infrastructure is needed.
Where do the signed documents live?
Documents are processed on Signbee’s platform (signb.ee). After both parties sign, a SHA-256 certified copy is emailed to everyone involved.
Are there any known limits?
The README does not mention specific limits. Only two-party signing is supported; the document expires after the optional expires_in_days parameter.
What transport or authentication is used?
The README does not specify transport or authentication details. It links to an OpenAPI spec (signb.ee/openapi) and the npm package for setup.
Frequently asked questions
What exactly does this server do?
It provides two MCP tools — send_document and send_document_pdf — that let an AI agent send a markdown document or an existing PDF for two-party e-signing, with signatures collected via email and a SHA-256 certified copy delivered.
What dependencies or runtime are required?
The server is available as an npm package (signbee-mcp). It requires an MCP-compatible client to invoke the tools; no additional signing infrastructure is needed.
Where do the signed documents live?
Documents are processed on Signbee’s platform (signb.ee). After both parties sign, a SHA-256 certified copy is emailed to everyone involved.
Are there any known limits?
The README does not mention specific limits. Only two-party signing is supported; the document expires after the optional expires_in_days parameter.
What transport or authentication is used?
The README does not specify transport or authentication details. It links to an OpenAPI spec (signb.ee/openapi) and the npm package for setup.
Basic information
More Files & Storage MCP servers
PDF Tools MCP
danielkennedy1
HTMLvault
AI tools (Claude, ChatGPT, Gemini, Grok, etc.) generate HTML constantly, from reports to landing pages to prototypes, but there's no easy way to share it or know if anyone looked. HTMLvault turns any HTML into a clean, t
mcp-rquest
xxxbrianA MCP server providing realistic browser-like HTTP request capabilities with accurate TLS/JA3/JA4 fingerprints for bypassing anti-bot measures. It also supports converting PDF and HTML documents to Markdown for easier processing by LLMs.
Bulk Filesystem Operations MCP Server
strawgateMCP Server for reading many files at the same time
Rust MCP Filesystem
rust-mcp-stackBlazing-fast, asynchronous MCP server for seamless filesystem operations.
Comments