PandaDoc MCP connector
The PandaDoc connector lets Claude, ChatGPT, Cursor, or any MCP client draft documents, fill fields, attach files, nudge signers, and read audit trails in PandaDoc, with each person signed in as themselves and every action recorded.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
126 tools
How to connect
How to connect PandaDoc to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect PandaDoc once
-
Open Connections, choose Add connection, and pick PandaDoc.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a PandaDoc API key. One person generates a token in PandaDoc and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Egnyte
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
PandaDoc MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
PandaDoc MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
PandaDoc MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect PandaDoc to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with PandaDoc through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Draft a proposal right after the call
Ask for a new PandaDoc document from your proposal template, filled with the customer name, pricing, and terms you just agreed, and have it dropped into the right deal folder.
-
Sales
Chase the quotes that have gone quiet
Check which PandaDoc documents are still sitting unsigned, see whether automatic reminders are switched on, and turn them on for the whole batch before the quarter closes.
-
Legal
Pull the full signing history of a contract
Get the audit trail for any PandaDoc contract, who opened it, who signed, and when, and have it summarized for a dispute or a compliance review.
-
Revenue operations
Correct fields across a batch of documents
When a price list or a company address changes, update the affected fields across many PandaDoc documents in one pass instead of opening each one.
-
HR
Send an offer letter with the right attachments
Create the offer letter from the standard template, upload the benefits summary and handbook as attachments, and add the standard clauses from the content library.
-
Customer success
Prepare renewals before the term ends
List the PandaDoc agreements expiring next month, download the signed copies for reference, and start renewal drafts linked to the matching customer records.
Try asking
- “Which PandaDoc documents are still awaiting signature?”
- “List document attachments added this week”
- “Show auto reminders status for open proposals”
Compare
Elaichi vs Zapier MCP vs Composio for PandaDoc
All three can connect PandaDoc to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over PandaDoc tools | Allow or restrict single PandaDoc tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per PandaDoc call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
PandaDoc tools for your AI agents
126 tools are ready to call through Elaichi's MCP endpoint the moment you connect PandaDoc, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting PandaDoc gets you
6 screens from the product, each doing one job for your PandaDoc account.
The agent
Ask about documents, read the answer.
Plain language questions return live PandaDoc documents, recipients and audit trails.
- documents
- templates
- attachments
- members
Ask Elaichi to work across your apps.
Which PandaDoc documents are still awaiting signature?
List document attachments added this week
Show auto reminders status for open proposals
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach PandaDoc.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
126 PandaDoc tools ready to call.
Documents, templates, attachments, members and reminders covered without custom code.
- List all PandaDoc members
- Get single PandaDoc member by ID
- List all PandaDoc attachment downloads
- List all PandaDoc auto reminders status
ElaichiToolsToolboxes
Every team gets its own toolbox.
Curate PandaDoc tools per team so Sales and Legal see different catalogs.
- Sales
- Legal
- Finance
- HR
ElaichiToolboxesShared connections
Teammates send documents, never touch credentials.
See who connected each PandaDoc account and which teams and members use it.
- Sales EMEA
- Sales AMER
- Legal
- Finance
ElaichiConnectionsAudit log
Answer who signed what, and when.
Append-only log of every PandaDoc call by time, person, action and resource.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest gets posted.
Fetch PandaDoc documents, group them, draft a digest, approve, post it back.
PandaDoc digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch documents
PandaDoc
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
PandaDoc
Queued
Collections and dashboards
Document numbers arrive before anyone asks.
Four metrics, 14 days of documents created and a team breakdown, computed on schedule.
PandaDoc health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Templates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales AMER 27%
Legal 21%
Finance 18%
FAQ
Frequently asked questions
How do I connect PandaDoc to Claude?
Connect PandaDoc in Elaichi first: PandaDoc signs in with an API key, which you paste into the connection screen, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi, and from then on it can work in PandaDoc as you.
Does PandaDoc work with ChatGPT and Cursor as well as Claude?
Yes. Once PandaDoc is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect PandaDoc once and every client you use picks it up.
What can an AI agent actually do with my PandaDoc data?
An agent can create draft documents in PandaDoc, fill and update fields, attach files, add content library items, move documents into folders, and link them to related records. It can also read document details, check and switch on automatic reminders, pull audit trails, download signed copies, and look up who is a member of your PandaDoc account. Short, concrete asks such as "turn on reminders for the Acme proposal" work better than long instructions.
Does connecting PandaDoc give the AI access to every document in the workspace?
No. The AI works inside the access of the person who signed in, so it sees the PandaDoc documents, templates, and folders that person can already reach and nothing more. Elaichi can narrow that further with restrictions, but it can never widen what PandaDoc itself allows.
Can I stop an agent from deleting or changing things in PandaDoc?
Yes. Restrictions in Elaichi apply per action, so you can allow reading PandaDoc document details and audit trails while blocking deletion of attachments or linked objects, or blocking edits altogether. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it.
What happens to a PandaDoc connection when someone leaves?
Offboarding that person in Elaichi ends their access to PandaDoc through every AI client at once. A PandaDoc connection they shared with a team keeps working for everyone else on it. If you want PandaDoc removed entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the PandaDoc MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. PandaDoc is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for PandaDoc?
Yes. Both let Claude, ChatGPT or Cursor use PandaDoc. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every PandaDoc call.
How is Elaichi different from Composio for PandaDoc?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to PandaDoc: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put PandaDoc in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.