GoodSign

io.goodsign由 goodsign.io 發布官方發布者v1.0.0更新於 Oct 28, 2026

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

已驗證Streamable HTTP可網頁執行效率與工作流商業與電商

概覽

AI 產生的概覽

GoodSign 電子簽章伺服器:讓助理送出待簽文件、追蹤簽署進度、提醒簽署人並下載已簽 PDF。

可以做什麼
  • 查看帳戶名稱與剩餘額度
  • 依狀態列出範本與文件,並取得某份文件或範本的完整詳情,包含簽署人鍵與欄位鍵
  • 把 PDF 上傳到短期連結並轉成 GoodSign 文件,依文字標籤自動建立欄位
  • 用範本送出文件請求電子簽章,或先存成草稿
  • 提醒尚未簽署的人、作廢已送出的文件,並取得 PDF 與稽核憑證的帶驗證下載連結
適用情境
適合需要在對話中送出合約、保密協議、工作說明書等文件請求簽署並追蹤進度時使用,也適合回答「還有哪些文件待簽」或取得已完成的簽署 PDF。
執行需求
遠端 streamable HTTP 端點 goodsign.io。需要 GoodSign 帳戶,並以 Authorization bearer 權杖形式提供 API 金鑰;每送出一個信封消耗 1 點額度。上傳 PDF 需另外對回傳的上傳連結發出 PUT,下載需在 shell 中以 curl 取得。
安裝前請注意
用範本送出會寄送真實郵件給收件人並消耗額度,呼叫前應確認簽署人姓名與電子郵件,或使用草稿模式。提醒會寄出真實郵件。作廢無法復原,且預設會通知簽署人。API 金鑰可存取帳戶內文件;下載連結同樣需要該 bearer 金鑰。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 GoodSign,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.goodsign%2Fgoodsign/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

工具

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

無需輸入參數。

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.

輸入參數doc_nameupload_id必填

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

無需輸入參數。

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.

輸入參數uuid必填

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.

輸入參數uuid必填

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.

輸入參數status

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.

無需輸入參數。

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.

輸入參數uuid必填signer_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.

輸入參數draftfieldssigners必填cc_emaildoc_nameemail_messageemail_subjectsend_in_ordertemplate_uuid必填

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.

輸入參數uuid必填notifymessage

版本歷史

1
  1. v1.0.0最新Sep 21, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。