6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Create, send and track documents for signature from your AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The PandaDoc MCP server connects PandaDoc e-signature to Claude, ChatGPT and any MCP-compatible agent. Eleven tools create documents, send them for signature, change their status and search the document archive — so contract work happens in conversation instead of a dashboard. Sign-in is OAuth, and the connector requests both read and write access to your account.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.document.draft to document.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.mcp.pandadoc.com and mcp.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.document.waiting_approval rather than document.sent, requiring a second send call after approval. An assistant reporting "sent" may mean "queued for approval".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.
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.
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.
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.
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.
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.
.md variant PandaDoc publishes for AI clients) · retrieved 2026-08-18developers.pandadoc.com/robots.txt allows /docs/ and carries no Content-Signal directives · retrieved 2026-08-18https://mcp.pandadoc.com/v1/mcp — HTTP 401 with an OAuth bearer challenge naming its resource descriptor (2026-08-18). The descriptor at https://mcp.pandadoc.com/.well-known/oauth-protected-resource/v1/mcp returned HTTP 200 and declares scopes read and write. The European endpoint behaved identically (2026-08-18). · retrieved 2026-08-18partner tier, 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-16www.pandadoc.com rate-limited our request (HTTP 429), so we did not confirm this page's contents directly · retrieved 2026-08-18Connect PandaDoc once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.