PandaDoc
NPM · @MINDSTONE/MCP-SERVER-PANDADOC · SCANNED AUG 3
PandaDoc document automation MCP server for Model Context Protocol hosts
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1855 tokens (~206/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mindstone/mcp-server-pandadoc
claude mcp add mindstone-mcp-server-pandadoc -- npx -y @mindstone/mcp-server-pandadoc
codex mcp add mindstone-mcp-server-pandadoc -- npx -y @mindstone/mcp-server-pandadoc
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindstone-mcp-server-pandadoc": {
"type": "local",
"command": [
"npx",
"-y",
"@mindstone/mcp-server-pandadoc"
],
"enabled": true
}
}
} openclaw mcp add mindstone-mcp-server-pandadoc --command npx --arg -y --arg @mindstone/mcp-server-pandadoc
mcp_servers:
mindstone-mcp-server-pandadoc:
command: "npx"
args: ["-y", "@mindstone/mcp-server-pandadoc"] {
"mcpServers": {
"mindstone-mcp-server-pandadoc": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-pandadoc"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +55
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: FSL-1.1-MIT functional
- 1 Aug 26 −1
- Dependency health: partial → unverified ▼ functional
- 31 Jul 26 −37
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@mindstone/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
configure_pandadoc_api_key ~100
Configure the PandaDoc API key. Call this tool when the user provides their PandaDoc API key. Get an API key from the PandaDoc Developer Dashboard: Settings → API → Developer Dashboard → Generate a Sandbox key (for testing) or Production key (for live use). Note: API access requires a PandaDoc Business or Enterprise plan.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | The PandaDoc API key from Settings > API > Developer Dashboard |
No output schema declared.
No examples provided.
create_document_from_template ~267
Create a new PandaDoc document from an existing template. Templates can contain fields, tokens (variables), pricing tables, images, and content placeholders. Pre-fill field values, set recipients, and customize content when creating. WORKFLOW: 1. Call list_templates to find the template ID 2. Create the document with this tool (pre-fill fields/tokens as needed) 3. Poll get_document_status until status is 'document.draft' 4. Use send_document to send for signing RELATED TOOLS: - list_templates: Find available templates and their IDs - get_document_details: See all fields/tokens after creation - send_document: Send the created document
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | — | Map of field names to values: { "FieldName": { "value": "text" } } |
| folder_uuid | string | — | Folder ID to store the document in |
| metadata | object | — | Custom key-value metadata to associate with the document |
| name | string | — | Document name |
| recipients | array | yes | Document recipients (at least one required) |
| tags | array | — | Tags to apply |
| template_uuid | string | yes | Template ID (from list_templates or PandaDoc app URL) |
| tokens | array | — | Template variables to pre-fill |
No output schema declared.
No examples provided.
download_document ~170
Download a PandaDoc document as a PDF file. Returns the file path where the PDF has been saved. The document must be in a completed or sent status to download. RELATED TOOLS: - get_document_status: Check document status before downloading - list_documents: Find document IDs
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document ID |
| separate_files | boolean | — | If true, downloads as a zip archive with separate PDFs per section |
| watermark_color | string | — | Watermark color as HEX code (e.g., "#FF5733") |
| watermark_font_size | number | — | Watermark font size |
| watermark_opacity | number | — | Watermark opacity (0.0 to 1.0) |
| watermark_text | string | — | Optional watermark text to overlay on the PDF |
No output schema declared.
No examples provided.
get_document_details ~104
Get full details for a PandaDoc document. Returns comprehensive data: recipients, fields, tokens, pricing, metadata, tags, linked objects, and more. Use this to inspect a document's content and state before sending or after completion. RELATED TOOLS: - list_documents: Find document IDs - get_document_status: Quick status check (lighter weight than full details) - send_document: Send the document for signing
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document ID |
No output schema declared.
No examples provided.
get_document_status ~166
Check the current status of a PandaDoc document. Returns: id, name, status, dates. Lightweight alternative to get_document_details. Use this to poll after upload/creation until status changes to 'document.draft'. Status values: document.uploaded, document.draft, document.sent, document.completed, document.viewed, document.waiting_approval, document.approved, document.rejected, document.waiting_pay, document.paid, document.voided, document.declined, document.error WORKFLOW — After upload: 1. Upload returns status 'document.uploaded' 2. Poll this tool every 2-3 seconds 3. When status is 'document.draft', the document is ready to send
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document ID |
No output schema declared.
No examples provided.
list_documents ~325
List and search PandaDoc documents with filtering. Supports filtering by status, template, name/reference, tags, metadata, date ranges, and more. Returns compact summaries: id, name, status, dates. Status codes: 0=draft, 1=sent, 2=completed, 3=uploaded, 4=error, 5=viewed, 6=waiting_approval, 7=approved, 8=rejected, 9=waiting_pay, 10=paid, 11=voided, 12=declined RELATED TOOLS: - get_document_details: Get full details for a specific document - get_document_status: Quick status check by document ID
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | — | Results per page (default 50, max 100) |
| created_from | string | — | Documents created on or after this date (ISO 8601) |
| created_to | string | — | Documents created before this date (ISO 8601) |
| folder_uuid | string | — | Filter by folder ID |
| order_by | string | — | Sort field. Prefix with - for DESC (e.g., "-date_created"). Default: date_status_changed |
| page | number | — | Page number (starts at 1) |
| q | string | — | Search by document name or reference number |
| status | number | — | Filter by status code (0=draft, 1=sent, 2=completed, etc.) |
| tag | string | — | Filter by tag |
| template_id | string | — | Filter by parent template ID |
No output schema declared.
No examples provided.
list_templates ~117
List available PandaDoc templates. Returns template IDs, names, and dates. Use template IDs with create_document_from_template. RELATED TOOLS: - create_document_from_template: Use a template ID to create a new document
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | — | Results per page (default 50, max 100) |
| folder_uuid | string | — | Filter by folder ID |
| page | number | — | Page number (starts at 1) |
| q | string | — | Search by template name |
| tag | array | — | Filter by tags |
No output schema declared.
No examples provided.
send_document ~301
Send a PandaDoc document to recipients for viewing/signing. The document must be in 'document.draft' status before sending. Optionally include a custom email message and subject line. ⚠️ WARNING — silent: true SUPPRESSES SIGNER NOTIFICATIONS. Setting silent: true tells PandaDoc to skip / suppress the email notifications that would normally be sent to every recipient. The document is still marked as sent on the PandaDoc side, but no signer notification email is delivered, which means recipients have no way of knowing the document is waiting for them unless they are notified through some other channel. Default is false (notifications are sent). Only pass silent: true when the user has explicitly asked you to skip / suppress the email notifications for this send. COMMON MISTAKES: - Cannot send a document in 'document.uploaded' status — wait for 'document.draft' - Cannot re-send a document that is already 'document.completed' or 'document.voided' RELATED TOOLS: - get_document_status: Verify document is in 'document.draft' before sending - get_document_details: Review document content before sending
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document ID |
| message | string | — | Email body message sent to recipients with the document link |
| silent | boolean | — | If true, suppresses email notifications to recipients. Default: false |
| subject | string | — | Email subject line |
No output schema declared.
No examples provided.
upload_document ~305
Upload a PDF, DOCX, or RTF file to PandaDoc to create a new document. The file is uploaded and converted into an interactive PandaDoc document. After upload, the document status is 'document.uploaded' and transitions to 'document.draft' after processing (typically 1-5 seconds). WORKFLOW: 1. Upload the file with this tool 2. Poll get_document_status until status is 'document.draft' 3. Then use send_document to send it for signing COMMON MISTAKES: - Don't try to send a document while it's still in 'document.uploaded' status — wait for 'document.draft' - File must be under 50 MB - Encrypted PDFs are not supported RELATED TOOLS: - get_document_status: Check when document is ready (status = 'document.draft') - send_document: Send the processed document for e-signature
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to the PDF, DOCX, or RTF file to upload |
| folder_uuid | string | — | ID of the PandaDoc folder to store the document in |
| name | string | — | Document name in PandaDoc (defaults to filename) |
| parse_form_fields | boolean | — | If true, recognizes PDF form fields as PandaDoc fields. Default: false |
| recipients | array | — | List of document recipients (at least one required for sending) |
| tags | array | — | Tags to apply to the document |
No output schema declared.
No examples provided.