Connect PandaDoc to Claude Code

Make Claude draft proposals and send them for signature in PandaDoc. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect PandaDoc to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect PandaDoc, you add a PandaDoc MCP server: a small hosted service that exposes PandaDoc's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own PandaDoc account. No API keys pasted into config files.

claude mcp add --transport http pandadoc https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in PandaDoc once connected?

Full read-write PandaDoc access lets Claude create a document from a template, populate tokens and pricing tables, add recipients and signing order, and send it for signature once you approve. The proposal and contract prep that used to mean clicking through the PandaDoc editor happens where the request already started.

Create a document from a template and populate its tokens
Fill in line items and pricing on a quote or proposal
Add recipients and set a signing order on a document
Send a prepared document for signature after you approve it
Send a reminder to a recipient who has not yet signed
Update a draft document's content or fields before it goes out

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same PandaDoc access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the PandaDoc API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when PandaDoc changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build PandaDoc connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same PandaDoc connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own PandaDoc account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on PandaDoc's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to PandaDoc?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the PandaDoc account it signs in with. Revoking access is one click in PandaDoc.

More on the PandaDoc connector

PandaDoc connector for claude.ai DocuSign + Claude Code Dropbox Sign + Claude Code Adobe Acrobat Sign + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us