Summary
A drafted agreement leaves the conversation signed.
The document you just wrote goes out for signature in the same turn — markdown is converted for you, and both sides get a certified copy back. The API key removes the sender's email confirmation step rather than unlocking the feature.
What it is
A send-for-signature call over Signbee. Hand it markdown or a PDF URL plus both parties' names and emails; Signbee converts, runs the signing ceremony, and emails a SHA-256 certified copy to each side.
What you get
- A markdown document converted to PDF and sent for two-party signing
- An existing PDF sent for signing from a publicly reachable URL
- A signing link with an expiry you set, defaulting to seven days
- A SHA-256 certified signed copy emailed to both parties
Requirements
Npx to run it. A Signbee API key in SIGNBEE_API_KEY sends documents straight away; without one, the sender confirms by email one-time code first.
Setup effort
One command — npx -y signbee-mcp