"Send the NDA to jane@acme.com." Your agent finds the template, fills in the signers and sends it — straight from Claude Code or any MCP client.
Already a customer? Set up in Settings → AI Agents.
The idea
MCP is the open standard that lets AI agents use real tools. Connect GoodSign and your agent can send documents from your templates, upload contracts it drafted itself, chase slow signers and pull down the signed PDF — while you stay in the conversation. Pay per document like everything else in GoodSign: one credit per envelope, no subscription.
Setup
Step 01
MCP switches on by itself for any account that has bought credits. Nothing extra to pay, no separate signup. Email John if you want to try it first.
Step 02
Grab a key at goodsign.io/apikeys. It authenticates your agent — revoke it there any time.
Step 03
One command in Claude Code, one in Codex — both speak HTTP natively, no bridge required.
Claude Code
claude mcp add --transport http goodsign https://goodsign.io/mcp \ --header "Authorization: Bearer YOUR_API_KEY"
Codex (CLI and app)
grep -q '\[mcp_servers.goodsign\]' ~/.codex/config.toml 2>/dev/null || printf '\n[mcp_servers.goodsign]\nurl = "https://goodsign.io/mcp"\n\n[mcp_servers.goodsign.http_headers]\nAuthorization = "Bearer YOUR_API_KEY"\n' >> ~/.codex/config.toml
Writes the four lines Codex needs into ~/.codex/config.toml. Check it with codex mcp list.
Anything else (stdio-only clients, via the bridge)
npx mcp-remote https://goodsign.io/mcp \ --header "Authorization: Bearer YOUR_API_KEY"
Invited accounts get these commands pre-filled with a real key in Settings → AI Agents.
The toolbox
Ten tools, each with instructions your agent understands — no docs to read, no glue code to write.
| Tool | What it does |
|---|---|
| list_templates | List your reusable templates |
| get_document | Template detail (signer keys) or live signing progress |
| list_documents | Documents by status — sent, complete, drafts |
| send_from_template | Send for signature — drafts, sequential signing, pre-filled fields |
| create_upload_url | Short-lived URL to upload a PDF the agent generated |
| create_document_from_upload | Turn an uploaded PDF into a document — tags become fields and signers |
| remind_signers | Nudge the people who haven't signed yet |
| void_document | Cancel a sent envelope |
| download_document | Download link for the signed PDF and audit certificate |
| account_status | Credits remaining |
The party trick
Not everything starts from a template. An agent can draft a Statement of Work, contract or NDA from scratch and send it straight through — it just embeds text tags in the signing block before exporting the PDF:
Signed for and on behalf of the Client: [sign|Client] [date|Client]
GoodSign finds the tags and places real signature, initial, date and text fields exactly there — however long the document runs. Because the agent wrote the document, it already knows every signatory's name and email, and the create_upload_url tool carries the full tag reference so agents get the syntax at the moment they need it.
Built careful
Auth is your API key over HTTPS — revoke it any time at /apikeys. Access is per-account, and included once you have bought credits.
Tools return document status and metadata — the PDF itself and signer-entered field values never enter your agent's context.
Sending and reminding email real people — agents are instructed to confirm with you first, and every account is rate limited.
Email from your GoodSign account address — invites usually go out same day.
Also built by us
It’s how we answer every GoodSign customer — live chat, email and the AI you already pay for, all in one inbox. One line of HTML and it’s on your site too.
All rights reserved © GoodSign Limited 2026
2 Stuart St, Ponsonby, Auckland 1011, New Zealand..