PandaDoc MCP Server for Cursor 10 tools — connect in under 2 minutes
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install PandaDoc and 2,500+ MCP Servers from a single visual interface.




{
"mcpServers": {
"pandadoc": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About PandaDoc MCP Server
Connect your PandaDoc account to any AI agent and automate your document workflows through natural conversation.
Cursor's Agent mode turns PandaDoc into an in-editor superpower. Ask Cursor to generate code using live data from PandaDoc and it fetches, processes, and writes — all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Documents — List, create from templates, send for signature, check status, and track viewed/completed/declined documents
- Templates — Browse all available document templates (proposals, contracts, NDAs, quotes)
- E-Signatures — Send documents for signature and monitor signing progress in real time
- Contacts — Manage recipient contacts with email, name, and company
- Team — List workspace members and their roles
The PandaDoc MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect PandaDoc to Cursor via MCP
Follow these steps to integrate the PandaDoc MCP Server with Cursor.
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
Save the file
Cursor will automatically detect the new MCP server
Start using PandaDoc
Open Agent mode in chat and ask: "Using PandaDoc, help me..." — 10 tools available
Why Use Cursor with the PandaDoc MCP Server
Cursor AI Code Editor provides unique advantages when paired with PandaDoc through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
PandaDoc + Cursor Use Cases
Practical scenarios where Cursor combined with the PandaDoc MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
PandaDoc MCP Tools for Cursor (10)
These 10 tools become available when you connect PandaDoc to Cursor via MCP:
pandadoc_create_contact
Email is required. Once created, patients can be used as recipients in document creation. Returns the created contact with their PandaDoc ID. Create a new contact in PandaDoc with email, name, and company for use as a document recipient
pandadoc_create_document
templateId is required (use pandadoc_list_templates to find). Recipients array must include at least email and optionally first_name, last_name, and role (matching template roles). The document is created in "uploaded" status and transitions to "draft" within 3-5 seconds. Fields is an optional JSON object to pre-fill template tokens/variables. Create a new PandaDoc document from a template with recipients, custom fields, and pricing — ready to send for signature
pandadoc_delete_document
This is irreversible. Only documents in draft or voided status should typically be deleted. Completed/signed documents should be voided first if deletion is required for compliance reasons. Permanently delete a PandaDoc document — this action cannot be undone and removes the document from all views
pandadoc_document_status
Returns current status, last viewed/completed dates, and recipient progress. Use for tracking: "has the client signed?", "did they view it?", or status polling after sending. Check the current status of a PandaDoc document — whether it is draft, sent, viewed, completed, or declined
pandadoc_get_document
Returns document name, status, all recipients with their signing status, template reference, pricing table totals, custom field values, and metadata. Use after listing documents to drill into a specific document for complete information. Get complete details of a specific PandaDoc document by ID, including recipients, fields, tokens, pricing, and audit trail
pandadoc_list_contacts
Returns contact name, email, company, and metadata. Contacts are the people your organization sends documents to. Use when the user asks about recipients, needs to find a contact email, or wants to review the contact database. List PandaDoc contacts with names, emails, companies, and associated document history
pandadoc_list_documents
Filter by status: draft (not yet sent), sent (awaiting signatures), completed (fully signed), viewed (opened by recipient), paid, voided, or declined. Returns document name, template used, status, total value, owner email, and dates. Use when the user asks about document pipeline, pending signatures, or completed agreements. List PandaDoc documents with name, status (draft/sent/completed/viewed/paid/voided/declined), creation date, and recipient info
pandadoc_list_members
Returns member name, email, role, and status. Use when the user asks about team members, document ownership, or needs to audit workspace access. List workspace members (users) in your PandaDoc organization with their email, role, and access level
pandadoc_list_templates
Returns template name, UUID (needed for pandadoc_create_document), creation date, and folder. Templates are reusable document blueprints with pre-defined layouts, fields, and recipient roles. Use when the user asks "what templates do we have?" or needs a template ID before creating a document. List all PandaDoc templates available for document creation — proposals, contracts, agreements, NDAs, and more
pandadoc_send_document
This triggers email notifications to all recipients. Set silent=true to suppress emails (useful when embedding signing in your own app). An optional message can be included in the notification email. The document moves to "sent" status after this call. Send a PandaDoc document for signature — transitions it from draft to sent and notifies all recipients via email
Example Prompts for PandaDoc in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with PandaDoc immediately.
"Show me all proposals waiting for signature"
"Create a new NDA for Jane Doe at Global Solutions."
"Did Acme Corp sign the contract I sent yesterday?"
Troubleshooting PandaDoc MCP Server with Cursor
Common issues when connecting PandaDoc to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
PandaDoc + Cursor FAQ
Common questions about integrating PandaDoc MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.Can Cursor use MCP tools in inline edits?
How do I verify MCP tools are loaded?
Connect PandaDoc with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect PandaDoc to Cursor
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.
