Skip to main content
Glama

Documenso MCP server

Documenso (Mojood Connect) MCP server

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.

Tools

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.

Related MCP server: kysigned-mcp

Try it locally

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.

The SAMPLE contracts

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.

Tests

uv run --env-file .env pytest            # unit tests (a fake Documenso API), plus live tests when the local Documenso runs

What a production version adds

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.

License

Apache 2.0. Documenso is a trademark of Documenso, Inc.; this project is not made or endorsed by Documenso, Inc.

Available Tools

6 tools
contact_documentsA contact's documentsA
Read-onlyIdempotent

Every document a person (or a company in its title) is part of, with their status on each.

Inputs: who (required). Returns: name, problem, documents

find_documentsFind documentsB
Read-onlyIdempotent

List documents with their status, when they were sent, each signer's status and who still has to sign.

Inputs: query, status. Returns: total, documents

get_documentRead a documentA
Read-onlyIdempotent

One document: its signers (signed, rejected with the reason, opened, not opened) and its history from Documenso's audit log.

Inputs: document_id (required). Returns: history, problem, document

needs_attentionWhat needs attentionA
Read-onlyIdempotent

Every signer still to sign, longest wait first (and which of them are our own people), rejected documents with the reason, and drafts not sent yet.

Inputs: no named parameters. Returns: drafts, waiting, rejected, waiting_on_us

send_draftSend a draft for signingA

Send a draft to its signers. The first call sends nothing and returns a summary and a confirmation code; it is sent only on a second call with the code, after the user has said yes.

Inputs: document_id (required), confirmation. Returns: done, problem, summary, document, +2 more

send_reminderSend a reminderA

Email a reminder to sign. The first call sends nothing and returns a summary and a confirmation code; the reminder goes only on a second call with the code, after the user has said yes.

Inputs: document_id (required), signer, confirmation. Returns: done, problem, summary, document, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes: find_documents lists broadly, get_document provides detail, contact_documents filters by person/company, and needs_attention aggregates pending/rejected/draft items. There is some overlap among the three listing tools, but their descriptions make the intended selection reasonably clear.

    Naming Consistency3/5

    Four tools follow a verb_noun pattern (find_documents, get_document, send_reminder, send_draft), but contact_documents and needs_attention break that convention. The snake_case style is consistent, yet the verb-first pattern is not.

    Tool Count5/5

    Six tools is a well-scoped size for a document-signing MCP server. Each tool covers a distinct read or action workflow without excessive surface area.

    Completeness3/5

    The set covers discovery, inspection, attention triage, reminders, and sending drafts. However, key lifecycle operations such as creating/uploading documents, canceling or voiding documents, and downloading completed files are missing.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.
      12
      252 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables management of e-signature envelopes — create, check status, list, send reminders, and void — through natural language.
      37
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.
      142
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to query, create, and manage contracts in plain English from any MCP client, including drafting and sending agreements, tracking renewals and signers, and building templates. It supports OAuth-authenticated workflows with safe defaults such as creating drafts and confirming before sending or changing live agreements.
      MIT