
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.
Basic information
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
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
More Files & Storage MCP servers
MCP Filesystem Server
mark3labsGo server implementing Model Context Protocol (MCP) for filesystem operations.
Filesystem MCP Server SSE
ysthinkThe SSE version of the MCP service is modified from the Filesystem MCP server
Google Drive MCP Server
hxie-pallasA google drive mcp servers based on Python
box-mcp-server
hmkA Box model context protocol server to search, read and access files

Google Drive
modelcontextprotocolModel Context Protocol Servers
Comments