Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | PandaDoc MCPShortlist candidate | tableauMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP PandaDoc · Publisher source ↗ | First-party MCP ecosystem:tableau · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 24, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 345 GitHub stars · checked 2026-09-24T04:14:47.698000Z |
| Shared repository stars | 2 Shared repository stars (not MCP-specific) · checked 2026-10-20 | Not documented |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | OAuth to the PandaDoc MCP endpoint; the user authorizes access to the PandaDoc account during connection. | The official package documents Tableau authentication and server connection configuration. |
| Cost | No separate MCP fee is documented. PandaDoc has a Free plan and paid Starter, Business, and Enterprise plans; product/feature availability depends on the account plan. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | Access is bounded by the authenticated PandaDoc account and its regional/server context. PandaDoc documents region-specific MCP servers that return only documents and templates stored in that region. | Tableau site roles, content permissions, and connected-data policies determine what the server can return. |
| Data handling | Not documented in the reviewed sources. The reviewed PandaDoc MCP documentation does not state an MCP-specific retention, training, or prompt-storage policy. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive analytics & data information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The MCP can work with PandaDoc business documents and templates. Depending on exposed tools and account permissions, document content and workflow metadata can be sensitive and actions may affect live document workflows. | Workbook metadata and query results may expose business-sensitive information or inherited data access. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-30 |
| Candidate evidence | 2026-10-20 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →