PandaDoc
by PandaDoc
Create, send and track documents for signature from your AI assistant. 11 tools, OAuth sign-in with read and write scopes, separate global and European servers.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect PandaDoc via MCP
https://mcp.pandadoc.com/v1/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
PandaDoc Tools & Capabilities (11)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- This connector can send documents for signature, and the write scope is not optional. PandaDoc's own resource descriptor declares
scopes_supported: ["read", "write"]— read from the server on 2026-08-18 — and the directory records the permission as "Read and write". There is no documented read-only mode. Grant it to an assistant only where you would grant it to a colleague. - No confirmation step is documented on PandaDoc's side. PandaDoc's MCP pages describe no server-side approval prompt before a send, and its prompt library shows sending as a one-line instruction. Whether you get asked first is decided by your MCP client's tool-approval settings. On a connector that mails contracts to third parties, check that setting before you connect.
- A send cannot be recalled by un-sending it. PandaDoc's API documentation describes sending as a status transition from
document.drafttodocument.sent, with recipients notified by email unless the caller sets silent delivery. Rolling one back is a new action, not an undo — and the recipient has already been emailed. - Two regions, and the directory only knows one. PandaDoc runs
mcp.pandadoc.comandmcp.pandadoc.eu. The European endpoint appears nowhere in Anthropic's 2026-08-16 directory snapshot, which PandaDoc confirms in its own documentation. Each server returns only its own region's documents. - Approval workflows change what sending does. Where a template has an approval workflow, PandaDoc documents the send moving the document to
document.waiting_approvalrather thandocument.sent, requiring a second send call after approval. An assistant reporting "sent" may mean "queued for approval". - Rate limits are per user and per operation. PandaDoc's API limits page gives 400 requests per minute for Send Document, 500 for create-from-template and 2000 for list and status calls, on a 60-second sliding window returning HTTP 429 above it. These are documented for API and OAuth keys; PandaDoc does not publish separate MCP figures.
- The plan requirement is not documented for MCP. PandaDoc's MCP prerequisites name only an account. Its API reference ties sandbox keys to the Enterprise plan, but that concerns API keys rather than the MCP OAuth flow, so we do not restate it as an MCP requirement.
- We did not read the tools and we called none of them. Our check was an anonymous handshake that returned HTTP 401. Every statement above about tool behaviour comes from PandaDoc's documentation or Anthropic's directory listing, each dated below. We never authenticated, and we never sent a document.
Frequently asked questions
Why does PandaDoc authentication fail even with the right password?
Almost always a region mismatch. PandaDoc runs two separate servers, and its troubleshooting page names a region mismatch as the most common cause of failed authentication. Accounts exist separately in each region, so the global server cannot authenticate a European account. If you sign in at app.pandadoc.eu, you must connect to the European URL.
Does the PandaDoc connector in Claude's directory work for EU accounts?
No. PandaDoc states plainly that there is no PandaDoc connector in the Claude directory for the European region, and that the listing you find by searching connects to the global server only. European accounts must add PandaDoc as a custom connector using the mcp.pandadoc.eu URL instead of installing the directory listing.
Will an AI assistant send a PandaDoc document without asking me first?
That depends on your MCP client, not on PandaDoc. The server exposes a send tool and PandaDoc's own prompt library shows a bare one-line instruction to send a named document to all its recipients. Nothing in PandaDoc's MCP documentation describes a server-side confirmation step, so the approval prompt is your client's responsibility.
Why are my documents or templates missing after connecting PandaDoc?
You are probably connected to the wrong region. PandaDoc documents that each regional server returns only the documents and templates stored in its own region, so a correct sign-in can still return empty results. PandaDoc also suggests checking that you authorised the account and workspace you expected during authentication.
Do you need a paid PandaDoc plan to use the MCP server?
PandaDoc's MCP prerequisites list only a PandaDoc account and its region, with no plan named. That is narrower than its REST API documentation, which ties sandbox API keys to the Enterprise plan. Since the MCP server uses OAuth rather than an API key, treat the plan question as unanswered by PandaDoc's published MCP docs.
Which AI tools work with the PandaDoc MCP server?
PandaDoc publishes setup steps for Claude Desktop, Claude Code, Cursor, VS Code, OpenCode and Codex. Its supported-clients page also lists ChatGPT, Windsurf and Google Antigravity, marking their instructions as in progress. PandaDoc adds that other clients can connect, though behaviour may be inconsistent — its own caveat, not ours.
Sources
- PandaDoc MCP overview (retrieved 2026-08-18 via the
.mdvariant PandaDoc publishes for AI clients) · retrieved 2026-08-18 - Getting Started with MCP (retrieved 2026-08-18) — prerequisites, per-client setup, the region table and the EU warning · retrieved 2026-08-18
- What You Can Do with PandaDoc MCP (retrieved 2026-08-18) — the prompt library behind the use cases above · retrieved 2026-08-18
- MCP Troubleshooting (retrieved 2026-08-18) — the source of four of the six questions above · retrieved 2026-08-18
- Supported MCP Clients (retrieved 2026-08-18) · retrieved 2026-08-18
- How to Send a Document via API (retrieved 2026-08-18) — status transitions, silent delivery and approval-workflow behaviour · retrieved 2026-08-18
- PandaDoc API limits (retrieved 2026-08-18) · retrieved 2026-08-18
- PandaDoc API reference (retrieved 2026-08-18) — the Enterprise-plan sandbox-key statement · retrieved 2026-08-18
- PandaDoc documentation index (retrieved 2026-08-18);
developers.pandadoc.com/robots.txtallows/docs/and carries noContent-Signaldirectives · retrieved 2026-08-18 - Anonymous MCP handshake against
https://mcp.pandadoc.com/v1/mcp— HTTP 401 with an OAuth bearer challenge naming its resource descriptor (2026-08-18). The descriptor athttps://mcp.pandadoc.com/.well-known/oauth-protected-resource/v1/mcpreturned HTTP 200 and declares scopesreadandwrite. The European endpoint behaved identically (2026-08-18). · retrieved 2026-08-18 - Anthropic Connectors Directory entry — — the eleven tool names,
partnertier, endpoint and transport above are read from our committed directory snapshot dated 2026-08-16; the directory page itself blocks automated fetches, so we did not retrieve it directly · retrieved 2026-08-16 - PandaDoc support (HTTP 200, 2026-08-18) · Privacy — , the value Anthropic's directory publishes;
www.pandadoc.comrate-limited our request (HTTP 429), so we did not confirm this page's contents directly · retrieved 2026-08-18
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- PandaDoc
- Tools
- 11
- Domain
- mcp.pandadoc.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.