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.

MCPs in this comparison

kordoctableau

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	kordocShortlist candidate	tableauMCP100 Recommended
Task fit
Best for	Parse and manipulate Korean HWP/HWPX and mixed office documents in local agent workflows Parse and manipulate Korean HWP/HWPX and mixed office documents in local agent workflows.	Business-intelligence discovery and analysis using authorized Tableau content.
Not ideal for	The MCP reads and can write local documents, including potentially sensitive government/business files. Use KORDOC_ROOT to constrain accessible paths, prefer offline mode for restricted environments, and treat OCR/parser inputs as untrusted files.	Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when	The MCP reads and can write local documents, including potentially sensitive government/business files. Use KORDOC_ROOT to constrain accessible paths, prefer offline mode for restricted environments, and treat OCR/parser inputs as untrusted files.	The connected identity is broader than the task requires Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details	Community implementation Chris Ryu / Community · 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,627 Shared repository stars (not MCP-specific) · checked 2026-10-20	Not documented
Shared-package downloads / 30 days	139,335 shared-package downloads / 30 days (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	No authentication is required for the local MCP process.	The official package documents Tableau authentication and server connection configuration.
Cost	No separate MCP fee is documented for the open-source package.	The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
Permissions	The MCP can read and write local documents. `KORDOC_ROOT` confines MCP file access to a directory and `KORDOC_OFFLINE=1` blocks outbound traffic.	Tableau site roles, content permissions, and connected-data policies determine what the server can return.
Data handling	Document parsing/OCR/rendering runs locally. Some OCR models can be downloaded at runtime unless offline mode is enabled.	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	Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.	Workbook metadata and query results may expose business-sensitive information or inherited data access.
Risk context	The MCP can process sensitive government/business documents and can fill, patch, redact, generate, and render files. Untrusted documents can be hostile inputs.	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 →