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 | Anytype MCPShortlist candidate | tableauMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Anytype · 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 | 534 GitHub stars · checked 2026-10-20 | 345 GitHub stars · checked 2026-09-24T04:14:47.698000Z |
| Package downloads / 30 days | 6,370 package downloads / 30 days · checked 2026-10-20 | No reliable download data |
| 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 | Anytype API key supplied as a Bearer authorization header to the local Anytype API. | The official package documents Tableau authentication and server connection configuration. |
| Cost | No separate MCP fee is documented for the open-source server/package. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | Authority follows the Anytype API key. The current wrapper exposes `auth_whoami` to inspect credential permissions; API-key management/pairing operations are intentionally excluded. | Tableau site roles, content permissions, and connected-data policies determine what the server can return. |
| Data handling | By default the MCP connects to the local Anytype API. File downloads are written to a private temporary directory. Debug logging explicitly omits authorization headers, arguments, payloads, and complete operation tables. | 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 create, edit, and delete knowledge-base objects and can download files. A leaked API key exposes the permissions granted to that key. | 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 →