Corpus vs UI5 MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Corpus vs UI5 MCP Server
In-depth architectural comparison of the Corpus and UI5 MCP Server 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
Corpus
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
UI5 MCP Server
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Corpus if you need specialized Developer Tools tools running via a local process. Choose UI5 MCP Server 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?
C
Choose Corpus 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).
Fuzzy full-text search over wiki, timeline, library books, articles, and news (~290 documents; token-AND with OR fallback)
get_entry
One wiki/timeline/articles/news entry as markdown with `claim_type`, `editorial_pass`, typed related-content edges, and canonical citation URLs; 9-language support via `lang
get_passage
A chapter of a digitized primary source text as numbered paragraphs with stable reference IDs (e.g. `GEN-1:26`); `ref` filters to one verse
get_source
Bibliography lookup by stable ID or search — every record carries the source-program classification (family, stance, relation), critical sources included
compare_traditions
Rows from the comparative datasets: flood-myths, divine-council-index, theomachy-crossrefs, world-ages, prophets-and-religions
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Corpus is categorized under Developer Tools and uses a local stdio subprocess. In contrast, UI5 MCP Server belongs to Developer Tools using local stdio subprocess. Select Corpus when you need capabilities focused on developer tools and UI5 MCP Server when you require tools for developer tools.
Typed 1-hop ego network of any corpus node (`see_also`, `in_body`, `cites_source`, `same_tradition`, `same_age`, `comparison_of`)
get_interpretation
The Wheel of Heaven framework's reading of a topic (curated context documents, or the closest wiki entry), always carrying an interpretation-layer notice
get_method
The editorial methodology: claim-type taxonomy, six-source rule, editorial passes — how to weigh everything else
get_glossary_term
Core terminology with renderings in all 9 site languages (exact-id match first)
UI5 MCP Server Tools (10)
create_integration_card
Scaffolds a new UI Integration Card.
create_ui5_app
Scaffolds a new UI5 application based on a set of templates.
get_api_reference
Fetches and formats UI5 API documentation.
get_guidelines
Provides access to UI5 development best practices.
get_integration_cards_guidelines
Provides access to UI Integration Cards development best practices.
get_project_info
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.