SignDocs Brasil MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SignDocs Brasil MCP Server create a signing session for proposal.pdf"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SignDocs Brasil — MCP Server
A Model Context Protocol server for the SignDocs Brasil e-signature API. It lets MCP-capable AI clients (Claude Desktop, Claude Code, Cursor, …) create signing sessions, manage multi-signer envelopes, upload/download documents, verify signatures, and manage webhooks — the same action catalog as the official n8n, Zapier, and Make.com integrations.
It is a thin adapter over the official @signdocs-brasil/api
SDK, which owns OAuth2 token exchange, caching, retries, and error handling.
Install
npm install -g @signdocs-brasil/mcp-server # or run on demand with npxRelated MCP server: Assinafy MCP Server
Credentials
Create an API credential in the SignDocs dashboard (app.signdocs.com.br → API) and expose it as environment variables:
Variable | Required | Default | Notes |
| yes | — | OAuth2 client id |
| yes | — | OAuth2 client secret |
| no |
|
|
| no | derived | override the resolved base URL |
| no | full set | space-separated scope override |
Start in
hml. HML data expires after ~7 days and is safe for testing. Switch toproductiononly when you intend to create real, legally-binding signatures.
Connect an AI client
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"signdocs": {
"command": "npx",
"args": ["-y", "@signdocs-brasil/mcp-server"],
"env": {
"SIGNDOCS_CLIENT_ID": "your_client_id",
"SIGNDOCS_CLIENT_SECRET": "your_client_secret",
"SIGNDOCS_ENVIRONMENT": "hml"
}
}
}
}Claude Code:
claude mcp add signdocs \
-e SIGNDOCS_CLIENT_ID=your_client_id \
-e SIGNDOCS_CLIENT_SECRET=your_client_secret \
-e SIGNDOCS_ENVIRONMENT=hml \
-- npx -y @signdocs-brasil/mcp-serverTools
Tool | Action | Safety |
| Create single-signer session, returns | ⚠️ binding + quota |
| Poll session status | read |
| Full session bootstrap | read |
| List by status | read |
| Cancel a session | ⚠️ irreversible |
| Resend OTP | write |
| Multi-signer envelope | ⚠️ binding + quota |
| Envelope details | read |
| Add a signer, returns | ⚠️ binding + quota |
| Combined stamped PDF URL | read |
| Attach a PDF to a transaction | write |
| Presigned download URLs | read |
| Search/list transactions | read |
| Transaction details | read |
| Cancel a transaction | ⚠️ irreversible |
| Cryptographic evidence | read |
| Public evidence verification | read |
| Public envelope verification | read |
| Detect signatures in a PDF | ⚠️ PROD-only + quota |
| Webhook management | mixed |
⚠️ tools carry destructiveHint annotations and a warning in their
description so compliant clients prompt the human before invoking them.
Annotations are only hints — review your client's auto-approval settings.
Not yet exposed
Trust sessions (/v1/trust-sessions) and resend-invite are not in
@signdocs-brasil/api v1.6.1 yet; they'll be added when the SDK supports them.
Digital ICP-Brasil A1 signing runs through the lower-level transaction/advance
flow rather than a hosted-session profile.
Resources
The server exposes grounding resources the model can read on demand:
signdocs://quickstart— the minimal signing flow + safety notessigndocs://policy-profiles— validpolicyProfilevalues and CUSTOM stepssigndocs://webhook-events— all subscribable event types
Remote HTTP transport (multi-tenant)
The same tools are also served over Streamable HTTP so a single deployment can serve many AI agents/tenants — each authenticates per session with its own SignDocs credentials (no shared secret baked into the server).
npm run start:http # or: signdocs-mcp-http (listens on PORT, default 3000)
# or containerized:
docker build -t signdocs-mcp . && docker run -p 3000:3000 signdocs-mcpEndpoint: POST /mcp (Streamable HTTP). Auth is required on the MCP
initialize request, via the Authorization header:
Authorization: Bearer <token>— a SignDocs OAuth2 access token (from/oauth2/token), passed straight through to the API.Authorization: Basic base64(clientId:clientSecret)— the server runs theclient_credentialsexchange for you.X-SignDocs-Client-Id+X-SignDocs-Client-Secret— the same client credentials as two plain headers (no base64), for header-only clients that can't transform values.
Pick the environment per session with X-SignDocs-Environment: hml|production
(defaults to the server's configured default).
The server behaves as an OAuth 2.0 Resource Server: it serves
GET /.well-known/oauth-protected-resource (RFC 9728, pointing at the SignDocs
authorization server) and answers an unauthenticated initialize with 401 +
WWW-Authenticate. The SignDocs API remains the authoritative token validator.
GET /healthz is an unauthenticated health probe.
Example client config (Bearer):
{
"mcpServers": {
"signdocs-remote": {
"type": "http",
"url": "https://your-host.example/mcp",
"headers": {
"Authorization": "Bearer <signdocs_access_token>",
"X-SignDocs-Environment": "hml"
}
}
}
}Server env vars: PORT, HOST, SIGNDOCS_ENVIRONMENT (default env),
MCP_PUBLIC_URL (for resource metadata behind a proxy), MCP_CORS_ORIGIN,
MCP_DNS_REBINDING_PROTECTION=true + MCP_ALLOWED_HOSTS / MCP_ALLOWED_ORIGINS
(recommended in production).
Sessions are held in process memory, so run a single instance or use sticky routing. For multi-instance/serverless, front it with sticky sessions or swap the session map for a shared store + EventStore (resumability). Deploying onto the existing
external-apiLambda + API Gateway as a NestedStack is the intended production path.
AWS Lambda
For serverless hosting, @signdocs-brasil/mcp-server/lambda exports
createLambdaHandler — an API Gateway HTTP API v2 handler that runs the MCP
transport statelessly (one server per invocation, no session store), with the
same Bearer/Basic auth. SignDocs hosts this on mcp-hml.signdocs.com.br /
mcp.signdocs.com.br.
import { createLambdaHandler } from '@signdocs-brasil/mcp-server/lambda';
export const handler = createLambdaHandler({ defaultEnvironment: 'hml' });Development
npm install
npm run build # tsc → dist/
npm test # vitest (pure unit tests, no network)
npm run inspect # build + launch MCP Inspector against the stdio serverRoadmap
v0.1: local stdio server, full tool catalog, env credentials.
v0.2 (this release): remote Streamable-HTTP transport with per-session, per-tenant auth (Bearer passthrough or Basic client-credentials) and OAuth Resource Server discovery. Tool layer is shared between both transports.
Next: deploy the HTTP transport onto
external-api(Lambda + API Gateway NestedStack); optional edge JWT validation + shared-store sessions for horizontal scale.
Available Tools
24 toolsadd_session_to_envelopeAdd signer to envelopeADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Add a signing session for one signer to an envelope. Returns IDs plus a ready-to-share signingUrl.
Inputs: signer (required), envelopeId (required), signerIndex (required), policyProfile (required), +4 more.
cancel_signing_sessionCancel signing sessionADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Cancel an active signing session. This cannot be undone.
Inputs: sessionId (required).
cancel_transactionCancel transactionADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Cancel a low-level transaction. This cannot be undone.
Inputs: transactionId (required).
create_envelopeCreate envelopeADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Create a multi-signer envelope around one PDF. After creating, add each signer with add_session_to_envelope. Consumes quota.
Inputs: signingMode (required), totalSigners (required), owner, locale, +9 more.
create_signing_sessionCreate signing sessionADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Create a single-signer "express" signing (or action-authentication) session and return its IDs plus a ready-to-share signingUrl (url + embed token). Consumes signature quota.
Inputs: signer (required), purpose (required), policyProfile (required), owner, +12 more.
delete_webhookDelete webhookADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Delete a registered webhook. Event delivery to it stops immediately.
Inputs: webhookId (required).
download_documentDownload documentARead-onlyIdempotentInspect
Get presigned download URLs for a transaction’s document and signed artifacts.
Inputs: transactionId (required).
get_envelopeGet envelopeARead-onlyIdempotentInspect
Get envelope details including per-signer session summaries and completion counts.
Inputs: envelopeId (required).
get_envelope_combined_stampGet envelope combined stampARead-onlyIdempotentInspect
Generate the combined stamped PDF (all signers) for a COMPLETED envelope and return a download URL.
Inputs: envelopeId (required).
get_evidenceGet evidenceARead-onlyIdempotentInspect
Retrieve the cryptographic evidence (hashes, step proofs, evidenceId) for a completed transaction.
Inputs: transactionId (required).
get_signing_sessionGet signing session detailsARead-onlyIdempotentInspect
Get full bootstrap data for a signing session (signer, steps, document, appearance).
Inputs: sessionId (required).
get_signing_session_statusGet signing session statusARead-onlyIdempotentInspect
Poll the current status of a signing session (ACTIVE/COMPLETED/CANCELLED/EXPIRED/FAILED).
Inputs: sessionId (required).
get_transactionGet transactionARead-onlyIdempotentInspect
Get full details of a single transaction, including its steps and results.
Inputs: transactionId (required).
list_signing_sessionsList signing sessionsARead-onlyIdempotentInspect
List signing sessions filtered by status, with cursor pagination.
Inputs: status (required), limit, cursor.
list_transactionsList / find transactionsARead-onlyIdempotentInspect
Search transactions by status, signer external ID, document group, or date range (cursor pagination). Use this to find a transaction or check signing history.
Inputs: limit, status, endDate, nextToken, +3 more.
list_webhooksList webhooksARead-onlyIdempotentInspect
List all registered webhooks for the tenant.
Inputs: no named parameters.
register_webhookRegister webhookAInspect
Register an HTTPS endpoint to receive event notifications. The response returns a signing secret — store it to verify the HMAC-SHA256 signature on incoming payloads.
Inputs: url (required), events (required).
request_document_uploadRequest a document upload linkAInspect
Get a one-time drag-and-drop upload page URL to give the user so they can upload a PDF directly to SignDocs (file bytes never pass through the chat). Use this when the document is a local file or a private Google Drive file — the user downloads it and drops it on the page. After they confirm the upload, pass the returned uploadToken to create_signing_session, create_envelope, or upload_document.
Inputs: filename.
resend_signing_session_otpResend signing session OTPAInspect
Resend the OTP challenge for a signing session, optionally over a specific channel (email/sms).
Inputs: sessionId (required), channel.
test_webhookTest webhookAInspect
Send a sample payload to a registered webhook and return the delivery result.
Inputs: webhookId (required).
upload_documentUpload documentAInspect
Upload a base64-encoded PDF to an existing transaction (≤10MB inline; use presign for larger).
Inputs: transactionId (required), filename, documentUrl, uploadToken, +1 more.
verify_documentVerify document signaturesADestructiveInspect
⚠️ This performs a consequential, possibly irreversible action (legally-binding signature request and/or quota consumption). Confirm with the human before calling. Inspect an uploaded PDF for embedded electronic/digital signatures. Requires PRODUCTION credentials + the verification:write scope and CONSUMES verification quota. Not available in HML.
Inputs: documentBase64 (required), filename.
verify_envelopeVerify envelope (public)ARead-onlyIdempotentInspect
Publicly verify all signers of an envelope and get consolidated download URLs.
Inputs: envelopeId (required).
verify_evidenceVerify evidence (public)ARead-onlyIdempotentInspect
Publicly verify a completed signature by its evidenceId. Returns status, document/evidence hashes, steps and signer display info. No authentication needed.
Inputs: evidenceId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Most tools have distinct purposes, but there is potential confusion between create_signing_session (single-signer express) and add_session_to_envelope (adds to envelope). Descriptions are clear enough to differentiate.
All tools follow a consistent verb_noun pattern (e.g., create_envelope, list_transactions, cancel_signing_session). No mixed conventions or inconsistent styles.
24 tools is on the higher side but justified for a comprehensive electronic signature service covering envelopes, sessions, transactions, documents, webhooks, and verification. Each tool addresses a specific need.
The surface covers most lifecycle operations: create, read, cancel, list for envelopes and sessions; upload/download documents; webhook management; verification. Minor gaps like updating envelope details or removing a session are not critical.
Related MCP Connectors
Send documents for legally valid e-signature in Brazil, track signers and status, and download signed files with Assinafy, a Brazilian e-signature platform with a free API plan (www.assinafy.com.br).
Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs.
Send documents for legally valid e-signature in Brazil, track signers and download signed files.
Create documents and reusable templates, request signatures, and track approvals — for AI agents.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.12252 npm1MIT

Assinafy MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables connecting to a Brazilian digital signature platform to prepare and send documents, track signatures, send reminders, and download signed copies.4MIT- FlicenseNot gradedqualityCmaintenanceEnables AI agents to create documents from templates, send them for legally valid Argentine electronic or digital signature, track status, download signed PDFs with audit certificates, and cryptographically verify signatures.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.1MIT