E-signature workflows using the Signbee MCP server. Send documents for legally binding signing with SHA-256 audit certificates from agent workflows.
Patterns for integrating legally binding e-signatures into agentic workflows using the Signbee MCP server.
Install the MCP server:
{
"mcpServers": {
"signbee": {
"command": "npx",
"args": ["-y", "signbee-mcp"],
"env": {
"SIGNBEE_API_KEY": "your-api-key"
}
}
}
}
| Tool |
|---|
| Purpose |
|---|
send_document | Send a document (markdown or PDF) to one or more signers |
get_document_status | Check signing progress and retrieve audit certificates |
list_documents | List all documents and their current status |
1. Draft a contract as markdown
2. Call send_document with signer email(s)
3. Signbee converts markdown to PDF automatically
4. Signers receive email with signing link
5. Poll get_document_status or listen for webhook callback
6. Download SHA-256 audit certificate on completion
Chain Signbee with other MCP servers for end-to-end deal automation:
Firecrawl MCP → scrape prospect info
↓
Gmail/AgentMail → send outreach email
↓
Cal.com MCP → book meeting
↓
Agent drafts contract as markdown
↓
Signbee MCP → send for signing
↓
Webhook → trigger next steps