SumoSign MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUMOSIGN_API_KEY | Yes | A scoped ss_live_... key from the SumoSign portal. | |
| SUMOSIGN_API_URL | No | Override for self-hosted or staging APIs. | https://api.sumosign.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upload_documentB | Upload a PDF from a local file path. Returns the document id used to create envelopes. |
| analyze_documentB | Analyze an uploaded PDF for field placement suggestions (text extraction, no OCR). Returns likelySigningPages, outline, and suggestions[] ready for create_envelope. |
| create_envelopeA | Create a signing envelope from an uploaded document (inline fields) or from a template (templateId + recipients). Returns the envelope in status draft. Sends Idempotency-Key automatically for safe retries. |
| create_templateA | Create a reusable template from an uploaded PDF that contains text anchors like {{signature_1}}. Returns parsed field coordinates. |
| list_templatesA | List reusable templates for the organization. |
| seed_starter_templatesB | Seed SumoSign sample templates (test envelope, simple NDA, one-page agreement) with baked-in anchors. |
| create_envelope_from_templateA | Create a draft envelope from a template. Provide recipients only — fields are inherited from the template. Sends Idempotency-Key automatically for safe retries. |
| preview_envelopeA | Download a placement preview of an envelope to a local file path: the PDF with every field drawn as a dashed, labeled box. Use it to verify signature placement with a human before send_envelope — no email is sent and no envelope is consumed. |
| send_envelopeA | Send a draft envelope. Returns 202 with { jobId, status: "queued", envelopeId }; token issuance and signing-invite emails run asynchronously. Poll get_envelope until recipients show status sent. Only humans can sign — this tool cannot complete a signature. Sends Idempotency-Key automatically for safe retries. |
| get_envelopeC | Get envelope status including per-recipient progress. Statuses: draft, sent, viewed, partially_signed, completed, voided, expired. |
| list_envelopesB | List the most recent envelopes for the organization. |
| void_envelopeA | Void an envelope before completion. Revokes all outstanding signing links. The reason is audit-logged. |
| get_audit_trailA | Get the append-only audit trail for an envelope: every event with timestamp and actor attribution (user, api_key, recipient, system). |
| download_signed_pdfC | Download the flattened, signed PDF of a completed envelope to a local file path. |
| download_certificateB | Download the Certificate of Completion (recipients, timestamps, IPs, event timeline, document hash) to a local file path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have distinct purposes, but create_envelope and create_envelope_from_template overlap in functionality (create_envelope also supports templates), potentially causing confusion for an agent.
All tools follow a consistent verb_noun pattern with snake_case (e.g., create_envelope, download_signed_pdf). Minor exception like seed_starter_templates is still clear.
15 tools cover the essential operations of an e-signature service without being excessive. Each tool serves a clear role in the envelope lifecycle.
The set covers the full envelope lifecycle from upload to download and audit. Minor gaps like the inability to update an envelope after creation are acceptable for a typical use case.