PandaDoc MCP

@PandaDoc list all documents sent in the last 30 days that are still waiting for signatures, grouped by recipient

Based on your PandaDoc account, here are 12 documents awaiting signatures from the past month: **Awaiting Client Signatures (8):** - MSA Amendment - Acme Corp (sent Jan 15, 2 reminders) - Q1 Consulting Agreement - Widget Inc (sent Jan 8, 1 reminder) - NDA - TechStart Labs (sent Jan 22, no reminders yet) [5 more listed] **Awaiting Internal Approvals (4):** - Sales Proposal - Enterprise Deal #4401 (sent to CFO Jan 10) [3 more listed] All documents include direct links to view status and send follow-up reminders.

This example assumes OAuth scope includes read access to documents and recipient data. PandaDoc's API returns metadata (status, dates, recipients) but not full document content. Rate limits apply if you're querying large document sets frequently — the free tier caps at 100 requests/hour.

@PandaDoc create a new NDA from our standard template for jane.smith@newclient.com and send it immediately

I've created and sent a new NDA document: **Document ID:** abc123xyz **Template Used:** Standard Mutual NDA (v3.2) **Recipient:** jane.smith@newclient.com **Status:** Sent (awaiting signature) **Expiration:** 30 days from today The document includes your company's pre-filled details (legal name, address) and a signature field for Jane. She'll receive an email with a signing link. You can track opens and completions in your PandaDoc dashboard or ask me for status updates.

This write action requires OAuth scope for document creation and sending. The MCP must know which template ID to use — either you specify it in the prompt or configure a default in your workspace settings. Sending immediately skips internal review, so confirm your template is finalized before automating this workflow.

@PandaDoc pull the last 5 signed contracts and summarize the payment terms and renewal clauses across all of them

I retrieved your 5 most recently signed contracts and analyzed the terms: **Payment Terms:** - 3 contracts: Net-30 invoicing, monthly billing - 1 contract: Quarterly prepayment required - 1 contract: Annual upfront payment with 5% discount **Renewal Clauses:** - 4 contracts: Auto-renew annually unless either party gives 60 days notice - 1 contract: Expires after 12 months, requires explicit renewal negotiation All 5 contracts include standard termination-for-cause language. Two contracts (Acme Corp, Widget Inc) have price escalation clauses tied to CPI.

This synthesis task combines the MCP's document retrieval with the AI's text analysis. The MCP fetches signed PDFs or structured field data; the AI extracts and compares clauses. Accuracy depends on whether your PandaDoc templates use consistent field names — unstructured PDFs require OCR-style parsing, which can miss nuances in legal language.

When PandaDoc MCP fits small client-services teams

A three-person creative agency sends 8-12 SOWs a month and needs the team to review terms before sending. The PandaDoc MCP works here if OAuth2 setup is straightforward and the MCP exposes document status, recipient tracking, and template access. The win is centralizing contract questions in Switchy instead of switching to the PandaDoc web app mid-conversation. The threshold: if your agency sends fewer than 5 contracts a month, the OAuth overhead probably isn't worth it—just paste the PandaDoc link into chat. If you send 15-plus and need audit trails, this MCP keeps the paper trail in one workspace and saves 10 minutes per contract cycle.

PandaDoc MCP for last-mile proposal edits

A 6-person sales team closes deals with custom proposals built in PandaDoc templates. Two AEs and the sales engineer need to finalize pricing tables and legal clauses in the final 48 hours before send. The PandaDoc MCP is the right call if it surfaces document fields, approval status, and recipient analytics without leaving Switchy. The team avoids the "who has the latest version" problem and keeps negotiation notes in the same thread as the proposal itself. The trade-off: if your proposals require heavy visual layout work or you're iterating on design, the MCP won't replace opening PandaDoc's editor. Use this for content and approval orchestration, not for pixel-pushing.

When PandaDoc MCP streamlines employee paperwork

A 12-person startup's HR lead sends offer letters, NDAs, and benefits forms through PandaDoc. Each new hire generates 4-6 documents that need tracking and follow-up. The PandaDoc MCP fits if it exposes document creation from templates, signing status, and recipient reminders. The HR lead can ask Switchy "which three candidates haven't signed their offer letters" and trigger reminders without opening a separate dashboard. The boundary: if you're onboarding one person every two months, the MCP setup isn't justified. If you're hiring two-plus people a month and juggling multiple document states, this MCP turns document admin into a chat query and cuts follow-up time by half.