O
OrestKlymko/penlydoc-mcp
Let an AI assistant send documents for e-signature with PenlyDoc and follow them:
updated 2026-10-25
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · OrestKlymko/penlydoc-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
OrestKlymko/penlydoc-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# PenlyDoc MCP server
Excerpted from the repository README (abridged)
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
1. Create an organisation at penlydoc.com (free) and copy an API key from Console → Developers.
2. Add the server to your MCP client's configuration:
json
"mcpServers": {
"penlydoc": {
"command": "npx",
"args": ["-y", "penlydoc-mcp"],
"env": { "PENLY_API_KEY": "sk_…" }
Node.js 18.17 or newer is needed. 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.
## Tools
| Tool | What it does | Side effects |
| get_organisation | Which organisation the key belongs to, sending limit | none |
| list_templates | Templates with their roles and data keys | none |
| send_from_template | Create a document from a template; send: true e-mails the people | e-mails real people |
| send_document | Upload local PDFs or photos and create a document; boxes from {{sig:1}} tags or coordinates | e-mails real people when send: true |
| list_documents | Documents with status and who has signed; filter by status or your reference | none |
| get_document | One document: each person, opened, signed or declined, and when | none |
| get_history | Hash-chained history with times and IP addresses | none |
| send_draft | Send a draft | e-mails real people |
| send_reminder | Remind everyone whose turn it is | e-mails real people |
| cancel_document | Void a document that is still being signed | cannot be undone |
| create_signing_link | One-hour link for an embedded signer | the link signs as that person |
| download_signed_pdf | Save the sealed PDF of a completed document to a file | writes a local file (never overwrites) |
"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
1. Create an organisation at penlydoc.com (free) and copy an API key from Console → Developers.
2. Add the server to your MCP client's configuration:
json
"mcpServers": {
"penlydoc": {
"command": "npx",
"args": ["-y", "penlydoc-mcp"],
"env": { "PENLY_API_KEY": "sk_…" }
Node.js 18.17 or newer is needed. 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.
## Tools
| Tool | What it does | Side effects |
| get_organisation | Which organisation the key belongs to, sending limit | none |
| list_templates | Templates with their roles and data keys | none |
| send_from_template | Create a document from a template; send: true e-mails the people | e-mails real people |
| send_document | Upload local PDFs or photos and create a document; boxes from {{sig:1}} tags or coordinates | e-mails real people when send: true |
| list_documents | Documents with status and who has signed; filter by status or your reference | none |
| get_document | One document: each person, opened, signed or declined, and when | none |
| get_history | Hash-chained history with times and IP addresses | none |
| send_draft | Send a draft | e-mails real people |
| send_reminder | Remind everyone whose turn it is | e-mails real people |
| cancel_document | Void a document that is still being signed | cannot be undone |
| create_signing_link | One-hour link for an embedded signer | the link signs as that person |
| download_signed_pdf | Save the sealed PDF of a completed document to a file | writes a local file (never overwrites) |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/orestklymko-penlydoc-mcp/)
- Source
- awesome · https://github.com/OrestKlymko/penlydoc-mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.