Documenso
Documenso is an open-source electronic signature platform that allows users to create, send, and sign documents digitally.
Verdict
Common use cases
- Send contracts for signature from chat
- Download signed PDFs after deal closes
- Check signature status during standup
- Duplicate last month's NDA for new hire
- Distribute urgent docs to pending signers
Integration
- Vendor
- Documenso
- Category
- other
- Auth
- API_KEY
- Tools
- 17
- Composio slug
documenso
Tools
- Create Embedding Presign Token V2 Beta
Tool to create a presign token for embedded authoring sessions. Use when initializing or renewing an embed session token.
- Delete Document Fieldsdestructive
Tool to delete one or more fields from a document. Use when you have confirmed the field IDs to remove. Supports single-field and batch deletion.
- Delete Templatedestructive
Tool to delete a template by ID.
- Distribute Document V2
Tool to distribute a document for signing. Use when you need to send a document to all or specific pending recipients.
- Download Signed Document
Tool to download a signed document file. Use when you need to retrieve the finalized PDF after a document has been signed.
- Duplicate Document V2
Tool to duplicate a document. Use when you need to create an exact copy of an existing document. Ensure the source document ID is valid before calling.
- Find Documents V2
Tool to find documents. Use when retrieving a paginated list of documents for operations requiring a document ID.
- Get Template
Tool to fetch a template by ID.
- List Templates
Tool to list templates. Use when fetching available templates with optional pagination.
- Move Document V2
Tool to move a document to a team. Use when transferring documents between personal and team accounts.
- Redistribute Document V2
Tool to redistribute a document to its pending recipients. Use when you need to re-send or re-distribute a sent document to recipients. Ensure the document has pending recipients or specific recipients selected before calling.
- Remove Team Member V1destructive
Tool to remove a member from a team.
- Resend Document For Signing V1
Tool to re-send a document for signing via POST /api/v1/documents/{id}/resend.
- Update Document Fields
Tool to update one or more fields on a document. Use when you need to adjust properties of existing fields post-creation.
- Update Document Recipient
Tool to update a document recipient. Use to change name, email, role, signing order or authentication options of a recipient.
- Update Document V2
Tool to update document properties. Use after confirming the document ID is valid.
- Use Template (v2-beta)
Tool to create a document from a template. Use when you need to instantiate a template with recipients and optional prefills.
Setup
Setup guide
- 11. In Switchy, click Integrations in the left sidebar, then find Documenso under Available MCPs. 2. Click Connect and choose API Key as the auth method. 3. Open your Documenso account settings, navigate to API Keys, and generate a new key with read and write permissions. 4. Paste the key into Switchy's prompt and click Authorize. 5. Switchy confirms the connection and shows Documenso's 17 tools in the integration panel. 6. Open any Space, type '@Documenso find my recent documents' and send. 7. If Documenso returns a list of documents, the connection works. 8. To invoke a tool, start your message with '@Documenso' followed by the task — for example, '@Documenso download the signed PDF for document ID abc123'. 9. The MCP fetches data and posts results inline. 10. If a command fails, check that your API key has the required scopes and hasn't expired.
What teammates see: by default, memories from Documenso are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Recent Documents
@Documenso find my recent documents, limit to 10 results, and show me the document ID, title, and current status for each.Open in a Space →
Send Document for Signing
@Documenso distribute document ID 7f3a9b2c to all pending recipients. Confirm when the emails have been sent.Open in a Space →
Download Signed Contract
@Documenso download the signed document for ID 4e8d1a6f and provide the file link so I can save it locally.Open in a Space →
Duplicate Existing Document
@Documenso duplicate document ID 2c5b9e1a and return the new document ID so I can update the recipient list.Open in a Space →
Remove Signature Field
@Documenso delete field ID 9a3f7c2e from document ID 6d1b4e8a and confirm the field has been removed.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Documenso find all documents sent in the last 7 days that are still pending signatures and show me who hasn't signed yet
Found 4 documents awaiting signatures from the past week: 1. **Q1 Consulting Agreement** (sent Jan 15) — pending: Sarah Chen (sarah@example.com) 2. **NDA - Acme Corp** (sent Jan 14) — pending: John Martinez (john@acme.co), Lisa Park (lisa@acme.co) 3. **Freelance SOW - Design Work** (sent Jan 12) — pending: Mike Thompson (mike@design.co) 4. **Office Lease Amendment** (sent Jan 11) — pending: Property Manager (leasing@building.com) All documents were distributed via email. You can send reminders or download drafts for any of these.
This example uses the Find Documents tool with date and status filters. The MCP returns metadata only—recipient names and emails come from the document's recipient list. You'll need read access to your Documenso workspace. Response time depends on your document volume; accounts with thousands of documents may see slower queries.
@Documenso duplicate the 'Standard NDA Template' document and send it to alex@newclient.com for signature, then let me know when it's distributed
Duplicated document ID `doc_abc123` from your Standard NDA Template. Distributed the new copy to: - **Alex Rivera** (alex@newclient.com) — role: Signer The recipient will receive an email with a signing link. The document is now in 'PENDING' status. You can track progress in your Documenso dashboard or ask me to check signature status later. Original template remains unchanged.
This chains the Duplicate Document and Distribute Document tools. The MCP creates a new document instance, then triggers email delivery—this is a write action that sends real emails to recipients. Ensure the recipient email is correct before running. If distribution fails (invalid email, account limits), the duplicate will exist but remain undistributed. Requires API key with document creation and distribution permissions.
@Documenso download the signed copy of document ID doc_xyz789 and summarize what was agreed to in the signature fields
Downloaded signed PDF (2.3 MB). Here's what the signature fields captured: **Signers:** - **Jane Doe** (Acme Corp) — signed Jan 16, 2025 at 10:42 AM UTC - **Robert Lee** (Your Company) — signed Jan 16, 2025 at 2:15 PM UTC **Key terms from visible fields:** - Effective date: January 20, 2025 - Contract value: $45,000 - Payment terms: Net 30 Both parties completed all required signature and date fields. The document is fully executed and stored in your Documenso workspace.
This uses the Download Signed Document tool to retrieve the finalized PDF, then the AI reads the file content to extract signature metadata and visible field values. Only works for documents in 'COMPLETED' status—pending or draft documents can't be downloaded as signed copies. The MCP returns the raw PDF; the AI's summary depends on how clearly the document's text and fields are structured. Large files (>10 MB) may hit processing limits.
Use-case deep-dives
When Documenso MCP replaces manual contract sends
A 6-person startup hiring 3 contractors per quarter spends 20 minutes per NDA: download template, fill placeholders, email, chase signatures. The Documenso MCP wins here if you already use Documenso as your signing tool. An agent can duplicate a template document, distribute it to the new hire's email, and poll for completion—all from a single prompt in Switchy. The threshold: if you're sending fewer than 5 NDAs a month, the setup overhead (API key, testing the duplicate-and-distribute flow) costs more than the 100 minutes you'd save. If you're above that line and your templates are stable, this MCP turns a 20-minute task into a 30-second agent call.
When embedded signing beats email ping-pong
A 3-person agency sends 8-12 proposals a month and loses deals when clients ghost the DocuSign email. The Documenso MCP's embedding presign token tool lets an agent generate a signing link you can paste directly into Slack or a CRM note—no inbox required. This works if your proposals are templatized and you're comfortable with the client signing in a browser tab instead of email. The trade-off: Documenso's embed flow requires the recipient to be online when you send the link (no async email fallback), so this scenario only fits synchronous handoffs like a live sales call or a Zoom closer. If half your clients sign 48 hours later, stick with email distribution.
When batch download saves compliance prep time
A 10-person SaaS company runs SOC 2 audits twice a year and needs to pull 40-60 signed vendor agreements from Documenso into a shared folder. The MCP's find-and-download tools let an agent search by date range, filter for completed documents, and batch-download PDFs in one prompt. This scenario assumes you're already tagging documents consistently in Documenso (the find tool respects your folder structure). The limit: if your document count exceeds 200 per audit period, the paginated find call gets slow and you'll want a dedicated export script instead of an agent. Below that threshold, the MCP turns a 90-minute manual pull into a 5-minute Switchy task.
Frequently asked
What does the Documenso MCP let me do in Switchy?
It lets your AI agents create, send, and track e-signature documents without leaving the chat. Agents can duplicate templates, add signing fields, distribute documents to recipients, and download the signed PDFs once complete. You stay in Switchy; the MCP handles the Documenso API calls in the background.
Do I need a paid Documenso account to use this MCP?
You need a Documenso account with API access. Documenso offers a free open-source tier and paid plans; check their pricing to confirm API keys are included. You'll paste that API key into Switchy's connection settings. No OAuth dance—just the key.
Can the MCP actually send documents to signers, or just create drafts?
It can send them. The Distribute Document tool pushes a document to all pending recipients or a specific subset. Once distributed, Documenso emails the signers directly. The MCP doesn't control reminder cadence or branding—that's set in your Documenso account settings.
Why use this instead of logging into Documenso directly?
Speed and context. If your agent is already drafting a contract or proposal in Switchy, it can generate the PDF, upload it to Documenso, add signature fields, and send—all in one thread. You avoid tab-switching and manual field placement. For one-off signatures, the Documenso UI is fine.
Who on my team should connect the Documenso account?
Whoever owns your Documenso workspace and can generate an API key. That person's key will be used for all MCP calls, so documents will appear under their Documenso account. If you need audit trails per user, connect separate Switchy workspaces with separate Documenso keys.