Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Documenso in Claude: see who hasn't signed, send reminders and drafts after a yes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DOCUMENSO_URL, DOCUMENSO_TOKEN, DOCUMENSO_SAMPLEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"documenso": {
"command": "uvx",
"args": [
"mojood-documenso-mcp",
"--stdio"
],
"env": {
"DOCUMENSO_URL": "your-value",
"DOCUMENSO_TOKEN": "your-value",
"DOCUMENSO_SAMPLE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add documenso --env DOCUMENSO_URL=your-value --env DOCUMENSO_TOKEN=your-value --env DOCUMENSO_SAMPLE=your-value -- uvx mojood-documenso-mcp --stdioFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"documenso": {
"command": "uvx",
"args": [
"mojood-documenso-mcp",
"--stdio"
],
"env": {
"DOCUMENSO_URL": "your-value",
"DOCUMENSO_TOKEN": "your-value",
"DOCUMENSO_SAMPLE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"documenso": {
"type": "stdio",
"command": "uvx",
"args": [
"mojood-documenso-mcp",
"--stdio"
],
"env": {
"DOCUMENSO_URL": "your-value",
"DOCUMENSO_TOKEN": "your-value",
"DOCUMENSO_SAMPLE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DOCUMENSO_SAMPLE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account askmojood, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DOCUMENSO_URL, DOCUMENSO_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Ask Claude about your contracts in plain words: which ones are still waiting, who hasn't signed (and who hasn't even opened them), what happened to one document. Send reminders and drafts from the same chat, with a confirmation step before any email goes out. There is no tool that signs on anyone's behalf.
Built by Mojood Connect as a working demo for Documenso. It runs against any Documenso through its v2 public API. This repository includes a local Documenso with SAMPLE contracts for a made-up company, Harbor Trading, and a local mail catcher, so you can try it without sending a single real email.
| Tool | What it does | Changes anything? |
|---|---|---|
find_documents | Documents by status or words in the title: when each was sent, every signer's status, who still has to sign | No |
get_document | One document: its signers (signed, rejected with the reason, opened, not opened) and its history from Documenso's audit log | No |
contact_documents | Every document a person, email or company is part of | No |
needs_attention | Every signer still to sign, longest wait first, our own people flagged; rejections with the reason; drafts not sent | No |
send_reminder | Email a reminder to sign, to one signer or everyone still to sign | Emails, after confirmation |
send_draft | Send a draft to its signers | Emails, after confirmation |
How sending is made safe. A call to send_reminder or send_draft without a confirmation sends nothing: it returns a plain summary ("Email a reminder to sign "Distribution agreement: Gulf Build Contracting" to Rashid Al-Mutairi (rashid@gulf-build.example), sent 8.0 days ago.") and a one-time code. The email goes only when the same request comes back with that code, within 10 minutes. A code works once, and only for the request it was issued for. The server's instructions tell the model to show the summary and wait for the user's yes. Documenso's own audit log records every reminder and send.
The server acts for the team that owns the API token.
Needs Docker (with Compose), uv, Python 3.13 and OpenSSL.
scripts/reset.sh # local Documenso on http://localhost:3020, filled with the SAMPLE contracts
uv run --env-file .env documenso-mcp # MCP server on http://127.0.0.1:8007/mcp (Streamable HTTP)
Every email Documenso sends lands in Mailpit at http://localhost:8026 and goes nowhere else. docker/compose.yml follows Documenso's own docker/production/compose.yml (v2.21.1), pinned, on 127.0.0.1 only. scripts/up.sh makes a self-signed signing certificate, signs the demo user up through Documenso's own sign-up endpoint and creates its API token the way Documenso stores them (the SHA-512 of the token); every secret stays in the git-ignored files docker/.env, docker/cert.p12 and .env, and nothing is printed.
Claude Desktop: add this to claude_desktop_config.json (Settings › Developer), with the path to this folder:
{
"mcpServers": { "documenso": { "command": "uv", "args": ["run", "--directory", "/path/to/documenso-mcp", "--env-file", "/path/to/documenso-mcp/.env", "documenso-mcp", "--stdio"] } } }
Then ask: "Which contracts are still waiting on signatures, and who hasn't signed?", "Where are we with the Gulf Build agreement?", "Remind Rashid to sign it."
Your own Documenso: set DOCUMENSO_URL, DOCUMENSO_TOKEN (an API token from your team's settings) and DOCUMENSO_SAMPLE=0.
Eight one-page SAMPLE documents for Harbor Trading: a supply agreement waiting on our own countersignature, an NDA opened but not signed, a distribution agreement the customer hasn't opened in eight days, an offer letter, two completed contracts, an NDA rejected for the wrong legal entity name, and a draft. Times are set relative to the moment it is seeded. Everyone and everything in it is made up.
uv run --env-file .env pytest # unit tests (a fake Documenso API), plus live tests when the local Documenso runs
This demo uses one team's API token. A production server for Documenso customers would add sign-in with each person's own Documenso account, so Claude sees exactly their teams; hosting with an audit log of every tool call; and more of the API (templates and "use template", envelopes with several files, fields, webhooks). That is what Mojood Connect builds.
Apache 2.0. Documenso is a trademark of Documenso, Inc.; this project is not made or endorsed by Documenso, Inc.