pandadoc-mcp

Name: pandadoc-mcp
Author: pandadoc

Sign documents, create contracts, and track approvals with PandaDoc.

От сообществаРаботаетБез входаГлобальныйБесплатноМожет изменять данные

Что умеет

Documents Audit Trail Get: Retrieve audit trail for a document.
Documents List: Paginated document listing with structured filters. Examples: 'list 50 Draft docs' · 'documents infolder abc-123 tagged onboarding' · 'page 3 of my docs' For natural-language queries,
Documents Search: Full-text search with status/date filters. Examples: 'NDA in completed docs' · 'modified 2026-01-01–2026-03-31' · 'sent docs Q1 2026' For natural-language queries, prefer ``ai_search

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Sign documents, create contracts, and track approvals with PandaDoc. Generate documents from templates, collect legally binding electronic signatures, manage workflows, and monitor status in real time.

Список инструментов сервера (23)

Технические названия из tools/list. Нужны только разработчикам.

documents_audit_trail_get	Retrieve audit trail for a document.
documents_list	Paginated document listing with structured filters. Examples: 'list 50 Draft docs' · 'documents infolder abc-123 tagged onboarding' · 'page 3 of my docs' For natural-language queries, prefer ``ai_search`` if available.
documents_search	Full-text search with status/date filters. Examples: 'NDA in completed docs' · 'modified 2026-01-01–2026-03-31' · 'sent docs Q1 2026' For natural-language queries, prefer ``ai_search`` if available.
documents_create	# Create document from an existing template. Create a new document in PandaDoc from an existing PandaDoc template.
documents_create_from_markdown	# Create document from markdown Create a new document in PandaDoc from markdown when there is only text representing the document content. Document content must be generated according to the guidelines below. The response includes a 'link' field with a direct URL to open the created document in PandaDoc. Document creation is asynchronous. After this tool returns, the document starts in Uploaded status and transitions to Draft after some time (or to Error if creation fails). The document must be in Draft status before it can be edited or sent. ## Markdown guidelines You can use standard CommonMark and GitHub-Flavored Markdown (tables, strikethrough, etc), plus the following custom extensions: ### Custom Syntax Extensions #### 1. Variables Variables are placeholder values that the document creator fills in PandaDoc before sending to recipients. Prioritize variables over fields for any value that the sender controls or pre-fills, even if it may be visible to recipients. Syntax: `[VariableName]` or `[Variable.Name]` or `[Multi.Part.Variable]` - Can include underscores, numbers, and multiple dot-separated parts Use variables for values controlled by the document creator: - Document metadata: `[Effective.Date]`, `[Agreement.Number]`, `[Contract.Value]` - Company/sender information: `[Company.Name]`, `[Company.Address]` - Pre-calculated values: `[Invoice.Total]`, `[Discount.Amount]` - Recipient information already known: `[Recipient.CompanyName]`, `[Recipient.FirstName]` Key principle: If the sender controls the value, use a variable. #### 2. Fields Fields are interactive form elements that recipients fill in or interact with during the signing process. Recipients see these as input boxes, checkboxes, or signature areas. Use fields for values controlled by the recipient: - Recipient signatures: `[[signature]]` - Recipient personal data they must enter: `[[text]]`, `[[email]]`, `[[phone]]`, `[[date]]` - Recipient choices/consents: `[[checkbox]]` - Information only the recipient knows or decides Key principle: If the recipient controls the value, use a field. Fields can be prefilled with default values, but are typically left empty for the recipient to fill. Syntax: `[[field_type attributes]]` Field Types: - `text` - Text input field - `email` - Email input field - `phone` - Phone number input field (`format` is required — see below) - `number` - Number input field - `date` - Date input field - `checkbox` - Checkbox field - `signature` - Digital signature field - `dropdown` - Dropdown selection field (`option` is required — see below) Attributes (HTML-style): - `required="true"` - Makes field required - `placeholder="text"` - Placeholder text - `checked="true"` - Pre-checked (checkbox only) - `value="timestamp"` - For date fields, use UNIX timestamp with millisecond precision (e.g., value="1718406000000"). For other fields, use plain text (e.g., value="John Doe"). - `format="US"` or `format="international"` - Required for `phone` fields. Must be exactly `"US"` or `"international"`. There is no default — omitting it causes a validation error. - `date_format="yyyy/MM/dd"` - Date format in ICU notation (e.g., `"dd/MM/yyyy"`, `"MM-dd-yyyy"`). Defaults to `"yyyy/MM/dd"` if omitted. - `option="Text"` - Required for `dropdown` fields. Repeatable — add one per option (e.g., `option="Yes" option="No"`). To assign a stable UUID to an option, use `option="uuid:Text"` format. - `id="Client_Text1"` - Specify an external ID that describes who should fill this field and what it represents (e.g., `id="Client_Signature"`, `id="Landlord_FullName"`, `id="Buyer_Email"`). Use the pattern `<RecipientRole>_<FieldPurpose>` so the field can later be assigned to the correct recipient. Multiple fields MAY share the same ID (they'll be synced — when one is filled, all are filled with the same value), but they MUST have the same type and attributes. Examples: - `[[text placeholder="Enter name"]]` - `[[email required="true" placeholder="Email address"]]` - `[[phone format="US"]]` - `[[phone format="international"]]` - `[[number]]` - `[[date required="true" value="1718406000000"]]` - `[[date date_format="dd/MM/yyyy"]]` - `[[checkbox checked="true"]]` - `[[dropdown option="Yes" option="No"]]` - `[[dropdown option="Yes" option="No" value="Yes" placeholder="Choose..."]]` Important: Fields with the same ID must have the same type and attributes. For example, you cannot have `[[text id="Field1"]]` and `[[email id="Field1"]]` in the same document as well as `[[text id="Field2" placeholder="Full Legal Name" ]]` and `[[text id="Field2"]]` because they have different attributes. Dropdown constraints: - At least one `option` attribute is required. - Option texts must be unique within the dropdown. - If `value` is set, it must match one of the defined option texts exactly; otherwise a validation error occurs. #### 3. Standalone Checkboxes Checkboxes use GFM syntax but can appear anywhere, not just in lists: - `[ ]` - Unchecked - `[x]` - Checked - Can be used inline, standalone, or in task lists #### 4. Page Breaks Syntax: `---` (three hyphens) creates a page break. IMPORTANT: Page breaks should be rare and intentional. Most documents don't need page breaks. Only use `---` when content must be on separate pages for a specific reason: - Legal/structural requirement - Document structure demands it Do NOT use `---`: - Between sections (use headings: `## Section Title`) - As visual decoration (use blank lines) - Simply because there's a section transition ### Limitations (Features NOT Supported) Do NOT include: - Blockquotes inside lists - Images inside links inline with text (e.g., `[![image](url)](link)`)
documents_update	Update a document. Document must be in Draft status. You can update text blocks, fields, and other document properties. After creating a new document, wait for it to reach Draft status before updating. To modify individual recipients, use `recipients_*` tools — the `recipients` param here replaces the entire list.
documents_status_change	Manually change a document's status. Only these transitions are allowed: Completed, Paid, Expired, or Declined. Status changes are restricted based on the current document status. Other statuses (such as Sent, Viewed, Approved) are set automatically by the system and cannot be set with this tool.
documents_send	Send a document to its recipients. The document must be in Draft status. After sending, the status changes to Sent and recipients receive a notification. Always confirm with the user before sending.
documents_status_get	Retrieve the overall document status (e.g. Draft, Sent, Completed, Expired). Some statuses are set automatically by the system: Sent (when the document is sent), Viewed (when a recipient opens it), Approved/Rejected (via approval workflows). For per-recipient signing progress use documents_details_get.
documents_details_get	Retrieve full document details including metadata, fields, tokens, pricing, and per-recipient status (who has signed, viewed, or is still pending). Use this tool when you need recipient-level progress.
documents_summary_get	Returns a summary for the specified document. Supports three granularity levels: detailed, short, or headline. If not ready, returns `{retry_after: N}` where N is seconds to wait before retrying.
documents_content_get	Returns the textual content of a document in plaintext or markdown format.
documents_metadata_get	Returns the AI metadata fields populated for the document. Each result combines the field definition (`id`, `key`, `field_type`, `settings`) with the extracted value (`value`, `acceptance_status`). When extraction is not done, returns a structured envelope `{code, description, retry_after?}` where `code` is one of: `extraction_pending` (in progress — retry after `retry_after` seconds), `not_started` (typically the document is not yet completed — retry once it is), or `failed` (do not retry; contact support).
documents_metadata_batch_get	Returns AI metadata for a list of 1-40 documents in a single request — the batch variant of `documents_metadata_get`. Prefer this tool over calling `documents_metadata_get` in a loop. The response is `{count, results[]}`; each entry is keyed by `document_id` and discriminated by `status` (`ok`, `extraction_pending`, `extraction_failed`, `extraction_not_started`, `not_found`, `access_denied`, `internal_error`). A failure for one document does not fail the whole request.
documents_fields_assign	Assign, reassign, or unassign document fields to recipients. The document must be in draft status. Provide a list of field-to-recipient mappings. Set recipient_id to null to unassign a field. Use get document details to obtain field UUIDs (fields[].uuid) and recipient IDs (recipients[].id).
documents_archive	Archive a document by ID. Uses PandaDoc delete endpoint with forever=false for reversible deletion.
recipients_edit	Update one recipient's details (email, name, phone, company, address, redirect) in place. Signers can be edited in Draft, Waiting Approval, Approved, Rejected, Sent, or Viewed status. A signer's email cannot be changed after they have signed. CC recipients can be edited in any status except Expired or Declined. Get recipient_id from document details first. Cannot use emails of existing contacts — use `recipients_reassign` for that.
recipients_add_cc	Add a CC (non-signing) recipient to a document. Requires an existing contact ID. Cannot add to Expired or Declined documents. Adding a contact that is already a CC recipient is silently ignored. This tool only adds CC recipients; signers must be set via `documents_create` or `documents_update`.
recipients_reassign	Replace a signer with another contact. Transfers all assigned fields to the new signer. The original signer is removed. Cannot reassign already-signed recipients. To just fix a signer's email/name, use `recipients_edit`.
recipients_delete	Remove a recipient from a document. Signers can only be removed in Draft status. CC recipients can be removed in any status except Expired/Declined.
templates_list	Retrieves a list of templates. You can filter results by a search query, tags, folder, or fields.
templates_create	Create a new template from a PDF URL. Provide a secure (HTTPS) publicly accessible URL to the PDF document.
templates_details_get	Get detailed information about a template including basic info, roles, fields, tokens, pricing, metadata, tags, content placeholders, and modification timestamps.