UI5 MCP Server vs Store Builder — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
UI5 MCP Server vs Store Builder
In-depth architectural comparison of the UI5 MCP Server and Store Builder 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
Store Builder
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose UI5 MCP Server if you need specialized Developer Tools tools running via a local process. Choose Store Builder 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, Store Builder belongs to Developer Tools using local stdio subprocess. Select UI5 MCP Server when you need capabilities focused on developer tools and Store Builder 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.
Store Builder Tools (29)
sb_connect
Log in, list the sites this account can operate, report which credentials are present
sb_site_list
List the sites this account can operate
sb_api_find
Find API operations by intent — one line per match — then read one operation's call sheet by id: real parameter schemas, the credential it needs, and the body's fields read off the handler that decodes them, each carrying the trap its own doc comment records
sb_api_call
Execute one operation. Defaults to a dry run that sends nothing
sb_page_open
Open a page for editing and return its outline
sb_outline
The open page as a compressed tree — never a raw document dump
sb_node_read
One node in full, with a warning if it is a shared global
sb_catalog_search
Find an element by what it should do, using the platform's own AI hints
sb_traits_for
An element's inspector — tabs, groups, controls and what each declared one writes — plus its AI hints, defaults and containment rules
sb_add
Add an element — or a whole nested subtree — in one call
sb_set
Write style/config/specials. Per breakpoint by default