PandaDoc — Claude Code MCP server: docs and e-signatures
Wires PandaDoc into your coding agent: build documents from templates, send them for signing, pull PDFs back. Useful when contracts live in PandaDoc.
claude mcp add --env PANDADOC_API_KEY=<PANDADOC_API_KEY> --env MCP_WORKSPACE_PATH=<MCP_WORKSPACE_PATH> --transport stdio pandadoc -- npx -y @mindstone/mcp-server-pandadocWhat PandaDoc does
The server exposes 15 tools to the agent. Documents can be listed and searched, checked for status, built from a template or an uploaded file, sent to recipients, shared as a view/sign link, and downloaded as PDF. Templates, folders, contacts and content library blocks each get their own tools.
It runs with npx -y @mindstone/mcp-server-pandadoc. You need Node.js 20+ and a PANDADOC_API_KEY from the Developer Dashboard, passed as an environment variable when you register the server.
One catch: create_document_from_url only takes a publicly reachable HTTPS PDF. The connector resolves the host's DNS and follows redirects itself, so the address has to open from the machine where the server runs. A local file or a link behind auth won't work there — use upload_document instead.
What it helps with
- generate a contract from a template with recipients and tokens filled in
- send a document out for signature and hand the client a link
- check where a document stands without opening the web app
- turn an existing PDF or DOCX into a PandaDoc document
- find a template or content library block by name
Example prompts for the agent
- Create a document from the
NDAtemplate, set the recipient from my contacts, and send it for signing - What's the status of the latest contract with this client?
- Download the signed document as PDF into the project
How to install PandaDoc
Platform CLI
claude mcp add --env PANDADOC_API_KEY=<PANDADOC_API_KEY> --env MCP_WORKSPACE_PATH=<MCP_WORKSPACE_PATH> --transport stdio pandadoc -- npx -y @mindstone/mcp-server-pandadocReplace <…> with your own values
Platform CLI
codex mcp add pandadoc --env PANDADOC_API_KEY=<PANDADOC_API_KEY> --env MCP_WORKSPACE_PATH=<MCP_WORKSPACE_PATH> -- npx -y @mindstone/mcp-server-pandadocReplace <…> with your own values
Config file
{
"mcpServers": {
"pandadoc": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-pandadoc"
],
"env": {
"PANDADOC_API_KEY": "<PANDADOC_API_KEY>",
"MCP_WORKSPACE_PATH": "<MCP_WORKSPACE_PATH>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"pandadoc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-pandadoc"
],
"env": {
"PANDADOC_API_KEY": "<PANDADOC_API_KEY>",
"MCP_WORKSPACE_PATH": "<MCP_WORKSPACE_PATH>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e PANDADOC_API_KEY=<PANDADOC_API_KEY> -e MCP_WORKSPACE_PATH=<MCP_WORKSPACE_PATH> pandadoc npx -y @mindstone/mcp-server-pandadocReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about PandaDoc
How do I install PandaDoc in Claude Code?
Run claude mcp add mcp-server-pandadoc -e PANDADOC_API_KEY=<PANDADOC_API_KEY> -- npx -y @mindstone/mcp-server-pandadoc with your own key.
What does this MCP server do?
It gives the agent PandaDoc access: documents from templates or files, sending for signature, plus folders, contacts and content library items.
What do I need before it works?
Node.js 20+ and a PANDADOC_API_KEY. Without the key the server can't reach the PandaDoc API.
