PandaDoc MCP Server
Connect PandaDoc to your AI agents with the PandaDoc MCP server.
Updated
What is PandaDoc MCP?
The PandaDoc MCP server is a Model Context Protocol server that connects PandaDoc to AI agents and assistants as a set of tools. With it connected, an agent can work with PandaDoc (esignature & documents — proposals, contracts, quotes, signing workflows) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the PandaDoc tools become available to the model.
Connect the PandaDoc MCP server
Connect PandaDoc MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the PandaDoc MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a PandaDoc tool to confirm the connection is live.
Connect PandaDoc MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add PandaDoc
Provide the PandaDoc MCP server URL or command and complete authentication.
- 3
Test
Reference PandaDoc from chat to confirm Cursor can reach the tools.
Sample use cases
An agent creates a PandaDoc proposal from a template when a CRM deal reaches the proposal stage
Instant proposal generation triggered by pipeline movement, no manual document creation.
An agent monitors PandaDoc document status and alerts the sales rep when a prospect opens or signs
Real-time visibility into document engagement without checking PandaDoc manually.
A scheduled agent checks for unsigned documents older than 5 days and sends a follow-up reminder
Automated follow-up on stalled proposals to reduce close-cycle time.
An agent pulls completed contract data from PandaDoc and updates the CRM with signed amounts and dates
Automatic CRM updates when deals close, keeping records in sync.
An agent generates a monthly report of documents sent, viewed, and signed with conversion rates
Document pipeline analytics without manual tracking or spreadsheet work.
An agent creates and sends an NDA from a PandaDoc template when a new vendor is onboarded
Standardized vendor onboarding with automated document workflow.
An agent extracts key terms (pricing, dates, clauses) from signed PandaDoc contracts for compliance tracking
Structured contract data available for reporting without manual review.
Using PandaDoc MCP with Gamut
On Gamut, the PandaDoc MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through PandaDoc and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What document operations does the PandaDoc MCP server support?
Agents can create documents from templates, send them for signature, track viewing and signing status, download completed documents, and extract document metadata. This covers the full proposal-to-signature lifecycle.
Can the PandaDoc MCP server handle e-signatures?
Yes. PandaDoc includes built-in e-signature capabilities. Agents can send documents for signature, track signing status, and get notified when all parties have signed.
Does the PandaDoc MCP server support document templates?
Yes. Agents can create new documents from existing PandaDoc templates, populating fields with data from other sources (CRM, databases). This enables automated proposal and contract generation.
Can I connect PandaDoc MCP to my CRM workflow?
Yes. In Gamut, agents can combine the PandaDoc MCP server with CRM servers to trigger document creation from deal stage changes, sync signed contract data back to the CRM, and automate the full deal-closing workflow.