GoodSign

io.goodsign/goodsign · v1.0.0

Send documents for e-signature, track and remind signers, and download signed PDFs.

MCPremoteAPI keyDocuments & PDFEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 10 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 84/100

What it does: 10 tools · 5 read, 5 write (incl. delete/pay) · Documents & PDF, Email

Test call list_documents: needs a key: HTTP 401 (1,012 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +6
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +10
Read/write annotations: +5
Safe test call: +8
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://goodsign.io/mcp

Tools

10 tools listed at last check

account_status Show the GoodSign account name and remaining credits. Each envelope sent costs 1 credit. Check this before bulk sending, or when the user asks "how many credits do I have?".
create_document_from_upload Turn a PDF you PUT to a create_upload_url url into a GoodSign document. Call this only after the PUT has finished successfully. GoodSign discovers any text tags in the PDF (see create_upload_url for the full TAG REFERENCE and rules) and creates one field per tag plus one signer per distinct signer k
create_upload_url Get a short-lived URL to upload a PDF that GoodSign will turn into a document. Use this for a document that is NOT based on an existing GoodSign template — e.g. a Statement of Work, contract or NDA drafted for this specific deal. After the PUT succeeds, call create_document_from_upload with the uplo
download_document Get an authenticated download URL for a document's PDF (including the audit certificate once complete). The URL requires the same `Authorization: Bearer` API key this MCP connection uses — download it with curl in a shell, do not try to fetch the bytes into the conversation.
get_document Fetch full detail for one document OR template by uuid. For a template: shows the signer keys ("key" on each signer) and field keys that send_from_template requires — always check this before sending. For a sent document: shows status and per-signer progress (who has signed, who is pending). Timesta
list_documents List this account's documents filtered by status. Use status "sent" (default) to see envelopes still waiting on signatures, "complete" for fully signed ones. Use this to answer questions like "what is still waiting to be signed?" — then get_document on a uuid for per-signer detail.
list_templates List the reusable document templates in this GoodSign account. Call this first whenever the user wants to send a document — send_from_template needs a template uuid from here. Each template defines signer keys; call get_document with the template uuid to see exactly which signer keys and field keys
remind_signers Re-send the signing invitation email to signers who have not completed yet. Omit signer_email to remind ALL pending signers of the document; pass signer_email to remind one specific person. Sends real email — do not call repeatedly; once per day per signer is plenty.
send_from_template Send a document for e-signature using a template. THIS EMAILS REAL PEOPLE and spends 1 credit — confirm each signer's name and email with the user before calling, or set draft=true to stage without emailing anyone. Requires one signers[] entry per signer key on the template (get_document on the temp
void_document Cancel a sent document so nobody can sign it anymore. This cannot be undone — to re-send, use send_from_template again. By default signers are notified the document was voided; set notify=false to void silently. Confirm with the user before voiding.

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/io.goodsign/goodsign.svg)](https://clawy.uk/mcp/s/io.goodsign/goodsign)

Website