PenlyDoc MCP server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PenlyDoc MCP serverSend the lease to Mia Novak from the Residential lease template"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PenlyDoc MCP server
Let an AI assistant send documents for e-signature with PenlyDoc and follow them: "Send the lease to Mia Novak from the Residential lease template, rent 950 EUR", "Who still has to sign order 42?", "Save the signed contract to ./signed".
It is a Model Context Protocol server that runs on your computer (stdio) and talks to the PenlyDoc REST API with your organisation's API key. Works with any MCP client.
Setup
Create an organisation at penlydoc.com (free) and copy an API key from Console → Developers.
Add the server to your MCP client's configuration:
{
"mcpServers": {
"penlydoc": {
"command": "npx",
"args": ["-y", "github:OrestKlymko/penlydoc-mcp"],
"env": { "PENLY_API_KEY": "sk_…" }
}
}
}Node.js 18.17 or newer is needed. (An npm release is coming; github: works today.) PENLY_URL points the server at another PenlyDoc instance (default https://penlydoc.com).
Treat the API key like a password: it can send documents in your organisation's name. Give the assistant a key of its own, so you can revoke it in the console without touching your other integrations.
Related MCP server: addsign-mcp
Tools
Tool | What it does | Side effects |
| Which organisation the key belongs to, sending limit | none |
| Templates with their roles and data keys | none |
| Create a document from a template; | e-mails real people |
| Upload local PDFs or photos and create a document; boxes from | e-mails real people when |
| Documents with status and who has signed; filter by status or your reference | none |
| One document: each person, opened, signed or declined, and when | none |
| Hash-chained history with times and IP addresses | none |
| Send a draft | e-mails real people |
| Remind everyone whose turn it is | e-mails real people |
| Void a document that is still being signed | cannot be undone |
| One-hour link for an embedded signer | the link signs as that person |
| Save the sealed PDF of a completed document to a file | writes a local file (never overwrites) |
| Check a signed PDF: seal intact, who signed | none, no key needed |
The server tells the assistant to confirm people, e-mail addresses and documents with you before anything is sent. Most MCP clients also ask you before each tool call; keep that on for the tools that e-mail people.
Learn more
MIT licensed.
This server cannot be deployed
Maintenance
Related MCP Connectors
Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
E-signature API for AI agents: send contracts, sign PDF documents, track and download signed files.
Automate eSignature workflows and signing tasks via natural language commands.
- SignvoyOAuthcom.signvoy
Send documents for e-signature, track signing status, and download signed PDFs. No API key required.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.820 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to send documents for e-signature, track signing status, remind pending signers, and download signed PDFs with audit-trail hashes via the AddSign API.642 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.142-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create fillable PDF forms, send contracts for electronic signature, verify signer identity via BankID or ID scan, and track document status after sending.MIT