In-depth architectural comparison of the UI5 MCP Server and Tableau Graphql MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
UI5 MCP Server
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Tableau Graphql MCP
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose UI5 MCP Server if you need specialized Developer Tools tools running via a local process. Choose Tableau Graphql MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose UI5 MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
UI5 MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Tableau Graphql MCP belongs to Developer Tools using local stdio subprocess. Select UI5 MCP Server when you need capabilities focused on developer tools and Tableau Graphql MCP when you require tools for developer tools.
Extracts metadata and configuration from a UI5 project.
get_typescript_conversion_guidelines
Provides guidelines for converting UI5 applications and controls from JavaScript to TypeScript.
get_version_info
Retrieves version information for the UI5 framework.
run_manifest_validation
Validates the manifest against the UI5 Manifest schema.
run_ui5_linter
Integrates with [`@ui5/linter`](https://github.com/UI5/linter) to analyze and report issues in the UI5 code.
Tableau Graphql MCP Tools (7)
graphql_query
Run **any** read-only Metadata API GraphQL query. The general tool for any lineage question.
introspect_schema
Live schema introspection: list entry points, or a type's exact fields.
lineage_examples
A schema cheat-sheet plus 28 curated question-to-GraphQL templates (8 categories).
where_used
Which workbooks/datasources use given column / field / table names (robust one-hop core-lineage resolution).
impact_analysis
Full transitive **multi-hop** blast radius of a column/field/table: every dependent field, plus affected sheets, dashboards, workbooks, and **owners to notify**.
search_content
Find content whose **name contains** a term (case-insensitive substring), across workbooks, datasources, tables (and optionally fields/columns), with coverage numbers.
server_info
Connected server, site, versions, endpoint, auth, and whether Catalog lineage is available.