ChatGPT + BoldSign: Why the Official MCP Server Doesn't Connect
Not directly. BoldSign has an official MCP server — but it’s a local stdio package (npx -y @boldsign/mcp), and ChatGPT connectors require a remote HTTP endpoint, so you can’t plug it into ChatGPT. There’s no BoldSign app in ChatGPT’s directory and no hosted endpoint like mcp.boldsign.com. The BoldSign MCP page describes the same local npm install — set a BOLDSIGN_API_KEY environment variable, pick your region, run it yourself — and contains zero ChatGPT connection instructions. It’s a real server, built for clients that speak local stdio (Claude Desktop, Cursor, and similar); ChatGPT just isn’t one of them. If you want ChatGPT touching your BoldSign account today, the honest route is a custom GPT with API actions.
Here’s what the official server actually is, what a custom GPT can do against BoldSign’s API, and where any chat setup runs out for signature ops.
What the official BoldSign MCP server actually is
Announced on BoldSign’s blog, the server wraps a useful slice of the API: list and get documents, revoke them, send reminders, list and get templates, send documents from templates, plus contacts, users, and teams. Notably, it sends from templates rather than composing arbitrary new envelopes.
The catch is deployment. It runs as a local process on your machine (or a server you manage), authenticated with your API key via environment variables. Claude Desktop and Cursor can launch and talk to local stdio servers; ChatGPT’s connector system only accepts remote MCP URLs. Until BoldSign hosts a remote endpoint, the official server and ChatGPT don’t meet.
Worth a footnote: BoldSign has been shipping its own in-product AI too — a Natural Language AI search across My Documents, Team Documents, and Templates, in beta per the developer changelog. That runs inside BoldSign and doesn’t connect your ChatGPT to anything.
How to set up the workaround: a custom GPT with API actions
- Generate an API key in BoldSign (the API docs cover key auth via
X-API-KEYand OAuth 2.0, with region-specific base URLs for US, EU, and CA). - In ChatGPT, create a custom GPT and add Actions against the BoldSign REST API — sending documents from templates, checking document status, and downloading signed PDFs are the endpoints that earn their keep.
- Store the API key in the GPT’s authentication settings, scoped as tightly as your plan allows.
- Ask it things like “what’s still unsigned from this week?” or “send the standard NDA template to this signer.”
This works, but it’s you maintaining an API integration — schema definitions, auth, error handling — for a chat that only answers when you open it.
The limits that actually matter
- The official MCP is out of reach. Local stdio only. No remote endpoint means no ChatGPT connector, full stop.
- No triggers. BoldSign’s real superpower is its webhooks — Sent, Viewed, Signed, Completed, Declined, Revoked, Expired, all HMAC-signed. ChatGPT can’t subscribe to any of them. A contract completing at 4pm sits unnoticed until someone opens a chat.
- Session-bound, even in agent mode. ChatGPT Work (launched July 9, 2026) runs long, usage-metered agent sessions — but you still start each one manually. It’s an errand, not a standing watch on your envelopes.
- Cross-stack follow-through stops at the chat. ChatGPT can tell you a document was signed; it won’t file the PDF in Drive, log it against the CRM record, and email the account owner on its own.
If you want BoldSign work that runs on its own: Carly
Signature workflows are almost entirely event-driven — a document gets signed, declined, or goes stale, and something should happen right then. That’s the exact shape ChatGPT can’t cover and BoldSign’s webhooks were built for.
Carly is an AI executive assistant that acts on triggers across your stack:
- When a contract completes, Carly can download the signed PDF and audit trail, file them in the client’s Drive folder, and email the account owner — minutes after the last signature lands.
- When a deal hits “Closed Won” in your CRM, send the standard MSA from a BoldSign template pre-filled with the contact’s details, and log the envelope ID back on the deal.
- Every morning, sweep documents stuck in progress past three days, fire BoldSign reminders, and drop a stalled-envelope summary into the exec brief.
- When a signer declines, create a task for the account owner with the decline reason and draft the follow-up email.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it.
- Actually sends — drafts and sends email across Gmail and Outlook, updates records, manages tasks.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly natively integrates with BoldSign.
ChatGPT vs Carly
| ChatGPT (custom GPT actions) | Carly | |
|---|---|---|
| Check document status, send from templates | Yes, in-session | Yes |
| Uses the official BoldSign MCP | No (local-only, not connectable) | Not needed — direct integration |
| Reacts when a document is signed or declined | No | Yes, on webhook triggers |
| Daily stalled-signature sweep, unprompted | No | Yes, on a schedule |
| Runs without a session open | No (agent runs are started + metered) | Yes (cloud, 24/7) |
| Files signed PDFs, updates CRM, emails owners | No | Yes |
| Setup | Build and maintain API actions | Describe it in plain English |
| Pricing | Paid ChatGPT plan | AI agents from $35/mo |
ChatGPT plus a custom GPT is a status console for envelopes you ask about. Carly is an assistant that runs the signature follow-through the moment events fire.
Frequently Asked Questions
Does ChatGPT work with BoldSign?
Not directly. BoldSign’s official MCP server is a local stdio package (@boldsign/mcp on npm) and ChatGPT connectors require a remote HTTP endpoint, so it can’t be added to ChatGPT. There’s no BoldSign app in the directory either. The workaround is a custom GPT with actions against BoldSign’s REST API.
What can the official BoldSign MCP server do, and who is it for?
It covers listing and fetching documents, revoking, sending reminders, template management, sending documents from templates, and contacts/users/teams. It’s built for local MCP clients like Claude Desktop and Cursor, authenticated with your API key via environment variables.
Can ChatGPT send a document for signature via BoldSign?
Only through a custom GPT you build against the API — BoldSign’s send-from-template endpoints work well for that. You maintain the actions and auth yourself, and it only runs inside a session you’ve opened.
Can ChatGPT notify me when a contract is signed?
No. BoldSign fires webhooks for Sent, Viewed, Signed, Completed, Declined, and more, but ChatGPT can’t subscribe to them. For “when it’s signed, file the PDF and email the owner,” you need a trigger-based assistant like Carly.
More: Claude + BoldSign · ChatGPT + DocuSeal · ChatGPT + PandaDoc · ChatGPT + Dropbox Sign · Can ChatGPT send emails · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
