GoodSign

io.goodsignPublished by goodsign.ioOfficial publisherv1.0.0Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

GoodSign e-signature server: send documents for signature, track signers, remind them, and download signed PDFs from an assistant.

What you can do
  • Check account name and remaining credits
  • List templates and documents by status, and fetch full detail on a document or template, including signer and field keys
  • Upload a PDF to a short-lived URL and turn it into a GoodSign document with fields discovered from text tags
  • Send a document for e-signature from a template, or stage it as a draft
  • Remind pending signers, void a sent document, and get an authenticated download URL for the PDF and audit certificate
When to use it
Useful when contracts, NDAs, statements of work or other agreements need to be sent for signature and tracked from a chat session, and when someone asks what is still awaiting signatures or wants the completed signed PDF.
Requirements
Remote streamable HTTP endpoint at goodsign.io. Requires a GoodSign account and an API key sent as an Authorization bearer token; each envelope sent costs one credit. Uploading a PDF needs a separate PUT to the returned upload URL, and downloads are meant to be fetched with curl in a shell.
Before you install
Sending from a template emails real people and spends a credit, so confirm signer names and emails or use draft mode. Reminders send real email. Voiding cannot be undone and notifies signers by default. The API key grants access to the account's documents; the download URL needs the same bearer key.

Installation

In SourceWeft

  1. Open GoodSign in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.goodsign%2Fgoodsign/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "goodsign": {
      "type": "http",
      "url": "https://goodsign.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

10

account_status

Account status and credits

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?".

Takes no parameters.

create_document_from_upload

Create a document from an uploaded PDF

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 key automatically. This does NOT send anything or email anyone — the result behaves like a template: check it with get_document, then send it with send_from_template. The created document can only be sent once — to send the same PDF again, upload it again with create_upload_url and call this tool a second time. If the response includes warnings about unreadable tags, fix the tag text in the source document, re-export the PDF, call create_upload_url again and retry.

Parametersdoc_nameupload_idrequired

create_upload_url

Get a URL to upload a PDF

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 upload_id this returns. The URL is valid for 15 minutes. If you are GENERATING the PDF yourself, embed text tags where fields should go — GoodSign places a real field at each tag's exact position, and each distinct KEY becomes one signer (reuse the same KEY on every tag that person fills). TAG REFERENCE — this is the complete list; any other tag type is discarded: - [sign|KEY] signature. [in|KEY] initials. Signature size variants: [signxs|KEY] [signsm|KEY] [signmd|KEY] [signlg|KEY] [signxl|KEY]. - [date|KEY] date of signing, filled in automatically. - [input|KEY] required text box. [input?|KEY] optional text box. [input|KEY|Some text] pre-filled, signer can edit. - [name|KEY] and [email|KEY] text boxes pre-filled with that signer's name / email address. - [c|KEY|Label] optional checkbox. [c*|KEY|Label] required checkbox. [c|KEY|x Label] pre-checked. [c1|KEY|Red] [c1|KEY|Blue] = radio group (same digit = one group, signer picks one). RULES — breaking any of these corrupts or silently drops fields: 1. KEY is the signer key: letters and digits ONLY (Client, signer1), identical spelling and case on every tag for that person. Keys differing only in case, spaces or punctuation collide into the wrong signer. Exception: trailing padding spaces before the closing ] (rule 4) are stripped before the key is matched, so [name|Client ] still keys to Client. 2. A tag must be one unbroken run of selectable text on a single line in a normal font — never an image, never wrapped across lines. 3. Do not use square brackets anywhere else in the document — prose like "[insert date]" gets parsed as a tag. Use parentheses instead. 4. The tag's printed size becomes the field's size: its font siz

Takes no parameters.

download_document

Get download link for a document PDF

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.

Parametersuuidrequired

get_document

Get document / template detail

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). Timestamps are unix epoch seconds. Field entries show structural info only (key, type, page, which signer); signer-entered field values are never returned.

Parametersuuidrequired

list_documents

List documents by status

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.

Parametersstatus

list_templates

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 it requires before sending.

Takes no parameters.

remind_signers

Remind pending 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.

Parametersuuidrequiredsigner_email

send_from_template

Send document for e-signature

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 template uuid lists the keys). For sequential signing set send_in_order=true: signers are emailed one at a time, in the order of the signers array (or explicit send_order values, lower first). Pre-fill text fields with fields[] using the field keys from get_document.

Parametersdraftfieldssignersrequiredcc_emaildoc_nameemail_messageemail_subjectsend_in_ordertemplate_uuidrequired

void_document

Void (cancel) a sent 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.

Parametersuuidrequirednotifymessage

Version history

1
  1. v1.0.0LatestSep 21, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.