Skip to main content
Glama
SumoSign MCP Server

SumoSign MCP Server

by meteordefect

@sumosign/mcp

MCP server exposing the SumoSign signing API to AI agents (Claude, ChatGPT, Copilot, and any MCP-compatible client) over stdio.

The API key authenticates the agent, not a signer. It can never complete a signature — signing is always done by a human recipient through their emailed, one-time link, with consent capture and an append-only audit trail.

Install & run

No install step is required; run it directly with npx:

SUMOSIGN_API_KEY=ss_live_... npx @sumosign/mcp

Hosted MCP (no local install)

If you do not want a local stdio process, attach the hosted server instead:

URL:     https://mcp.sumosign.app/mcp
Header:  Authorization: Bearer ss_live_YOUR_KEY

Same URL works in Grok Bot (Plugins → Add custom), grok.com Connectors, Claude (OAuth via the Connectors Directory), and any MCP host that speaks Streamable HTTP. Create a scoped key at app.sumosign.app/keys.

The stdio instructions below remain the primary path for Cursor and other local agents.

Configuration

Env var

Required

Default

Description

SUMOSIGN_API_KEY

yes

—

A scoped ss_live_... key from the SumoSign portal.

SUMOSIGN_API_URL

no

https://api.sumosign.app

Override for self-hosted or staging APIs.

Client config example

{
  "mcpServers": {
    "sumosign": {
      "command": "npx",
      "args": ["-y", "@sumosign/mcp"],
      "env": { "SUMOSIGN_API_KEY": "ss_live_..." }
    }
  }
}

Related MCP server: zyta-sign-mcp

Tools

The server registers 16 tools:

Documents

  • upload_document — upload a local PDF; returns the document id used to create envelopes.

  • analyze_document — analyze an uploaded PDF for field-placement suggestions (text extraction, no OCR).

Templates

  • create_template — create a reusable template from a PDF with text anchors like {{signature_1}}.

  • list_templates — list the organization's reusable templates.

  • seed_starter_templates — seed sample templates (test envelope, simple NDA, one-page agreement).

Envelopes — create

  • create_envelope — create a draft envelope from an uploaded document (inline fields) or a template.

  • create_envelope_from_template — create a draft envelope from a template; fields are inherited.

Envelopes — verify & send

  • preview_envelope — download a placement preview (every field drawn as a dashed, labeled box) to a local path. No email is sent and no envelope is consumed — use it to confirm placement with a human before sending.

  • send_envelope — send a draft envelope. Only humans can sign; this tool cannot complete a signature.

Envelopes — track

  • send_reminder — re-send the signing email to outstanding recipients. 24h cooldown; spend and spam caps apply. Cannot complete a signature.

  • get_envelope — get envelope status including per-recipient progress.

  • list_envelopes — list the most recent envelopes for the organization.

  • void_envelope — void an envelope before completion; revokes outstanding signing links (audit-logged).

  • get_audit_trail — get the append-only audit trail with actor attribution.

Downloads

  • download_signed_pdf — download the flattened, signed PDF of a completed envelope to a local path.

  • download_certificate — download the Certificate of Completion to a local path.

Security

  • Local filesystem access. upload_document reads a local PDF path you provide, and preview_envelope, download_signed_pdf, and download_certificate write files to local paths you provide. The server can therefore read and write any file the host process can reach. Run it with least privilege and only point it at paths you intend to share.

  • Untrusted document content / prompt injection. analyze_document extracts text from PDFs and returns it to the agent. Document contents are untrusted input and may contain prompt-injection attempts. Treat extracted text as data, not instructions, and keep a human in the loop before send_envelope.

  • Least-privilege API keys. Issue a scoped key per agent from the SumoSign portal and grant only the scopes that agent needs. Available scopes: documents:create, documents:read, documents:send, documents:download, templates:read, templates:write, signers:manage, webhooks:write, audit_logs:read, branding:write, voice:trigger. Keys are hashed at rest and revocable, and can never complete a signature on a human's behalf.

About

SumoSign is developed by Cipher Projects.

License

MIT

Available Tools

15 tools
analyze_documentB

Analyze an uploaded PDF for field placement suggestions (text extraction, no OCR). Returns likelySigningPages, outline, and suggestions[] ready for create_envelope.

Inputs: documentId (required).

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.

Inputs: name (required), recipients (required), fields, message, +5 more.

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.

Inputs: name (required), recipients (required), templateId (required), message, +3 more.

create_templateA

Create a reusable template from an uploaded PDF that contains text anchors like {{signature_1}}. Returns parsed field coordinates.

Inputs: name (required), documentId (required).

download_certificateB

Download the Certificate of Completion (recipients, timestamps, IPs, event timeline, document hash) to a local file path.

Inputs: envelopeId (required), outputPath (required).

download_signed_pdfC

Download the flattened, signed PDF of a completed envelope to a local file path.

Inputs: envelopeId (required), outputPath (required).

get_audit_trailA

Get the append-only audit trail for an envelope: every event with timestamp and actor attribution (user, api_key, recipient, system).

Inputs: envelopeId (required).

get_envelopeC

Get envelope status including per-recipient progress. Statuses: draft, sent, viewed, partially_signed, completed, voided, expired.

Inputs: envelopeId (required).

list_envelopesB

List the most recent envelopes for the organization.

Inputs: no named parameters.

list_templatesA

List reusable templates for the organization.

Inputs: no named parameters.

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.

Inputs: envelopeId (required), outputPath (required).

seed_starter_templatesB

Seed SumoSign sample templates (test envelope, simple NDA, one-page agreement) with baked-in anchors.

Inputs: no named parameters.

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.

Inputs: envelopeId (required), idempotencyKey.

upload_documentB

Upload a PDF from a local file path. Returns the document id used to create envelopes.

Inputs: filePath (required).

void_envelopeA

Void an envelope before completion. Revokes all outstanding signing links. The reason is audit-logged.

Inputs: reason (required), envelopeId (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    15 tools cover the essential operations of an e-signature service without being excessive. Each tool serves a clear role in the envelope lifecycle.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    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
      C
      quality
      D
      maintenance
      Enables AI agents to manage Zyta Sign documents, signatures, and studies with secure authentication and permission-respecting operations.
      49
      7 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send documents for e-signature, track signing status, remind pending signers, and download signed PDFs with audit-trail hashes via the AddSign API.
      6
      49 npm
      MIT