UI5 MCP Server vs PromptEden
A side-by-side look at the UI5 MCP Server and PromptEden MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
PromptEdenDeveloper Tools · Local subprocess (stdio)Stdio MCP server for PromptEden projects, monitors, answers, and analytics.53GoodAuth: api key requiredVerdict: choose UI5 MCP Server for developer tools work as a local process; choose PromptEden for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose UI5 MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get_guidelines, run_ui5_linter, get_api_reference.
PChoose PromptEden when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PROMPTEDEN_API_KEY, PROMPTEDEN_BASE_URL. - You want tools like
get_account, list_monitors, get_results.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P PromptEden | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 68/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | PROMPTEDEN_API_KEYPROMPTEDEN_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 103 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 10 | 29 |
| Full listing | View UI5 MCP Server | View PromptEden |
Tools & capabilities
UI5 MCP Server tools 10
get_guidelinesThis tool MUST be called once to retrieve UI5 guidelines before working on any UI5 (SAPUI5/OpenUI5) related task or project or creating a UI5 project. The guidelines provided by this tool MUST be followed to ensure best practices and avoid common pitfalls in UI5 development.run_ui5_linterRun UI5 linter on a UI5 project to find and optionally fix UI5 related problems like the usage of deprecated API. After making changes, you should always run the linter again to verify that no new problems have been introduced.get_api_referenceSearch the UI5 API reference for module names and symbolsget_project_infoGet general information about a local UI5 project.create_ui5_appCreate a new basic SAPUI5 application implemented in TypeScript or JavaScriptget_version_infoGet version information for UI5 (OpenUI5 or SAPUI5)get_integration_cards_guidelinesThis tool MUST be called once to retrieve Integration Cards guidelines before working on any Integration Card related task or creating an Integration Card. The guidelines provided by this tool MUST be followed to ensure best practices and avoid common pitfalls in Integration Cards development.Integration Cards are also called 'UI Integration Cards' or 'UI5 Integration Cards'.create_integration_cardCreate a new Integration Card, UI Integration Card, or UI5 Integration Cardrun_manifest_validationValidates UI5 manifest file. After making changes, you should always run the validation again to verify that no new problems have been introduced.get_typescript_conversion_guidelinesThis tool MUST be called once before converting a UI5 (SAPUI5/OpenUI5) project from JavaScript to TypeScript. The instructions provided by this tool MUST be followed to ensure that the project setup and code is correctly converted.
PromptEden tools 29
get_accountGet PromptEden team, plan, and usage details via GET /api/v1/account. Does not use credits.list_monitorsList PromptEden monitors for the authenticated team via GET /api/v1/monitors. Does not use credits.get_resultsGet monitor results by monitor UUID via GET /api/v1/monitors/:monitorId/results. Does not use credits.list_providersList the answer engines available for monitors, with key, name, category, and costTier. Coding-agent providers are omitted. Use a returned key when creating a monitor target. Does not use credits.list_projectsList projects via GET /api/v1/projects. Does not use credits.get_projectGet a single project by id, UUID, or slug via GET /api/v1/projects/:projectId. Does not use credits.agent_statusGet the authenticated agent/key status via GET /api/v1/agent/status. Requires account:read scope. Does not use credits.analytics_get_propertyGet the analytics property for a project via GET /api/v1/analytics/property: hostname, property state, collector state (six-state enum: not_set_up, awaiting_first_collection, healthy_zero, healthy_data, stale, failed) and the latest verification run. Never returns the site key. 409 property_scope_a…analytics_get_verificationPoll the latest snippet verification run for a project's analytics property via GET /api/v1/analytics/property/verification. Read-only: never starts or retries a run. Statuses: queued, running, succeeded, failed, expired; checks cover script load and collector endpoint. Does not use credits.analytics_get_trafficGet the AI-referral Traffic report via GET /api/v1/analytics/traffic: totals, per-engine series, landing pages, channel split, evidence provenance and sampling flags. HONESTY: `totals: null` means the collector has no basis to report (check collector.state) — it is NOT zero traffic; only healthy_ze…analytics_get_overviewGet the GA Overview via GET /api/v1/analytics/overview: visits · AI visits · goal completions chain, top engines and landing pages, goals summary, instrumentation card, six-state collector + freshness. HONESTY: `totals: null` means the collector has no basis to report (check collector.state) — NOT…analytics_list_goalsList destination-URL goals via GET /api/v1/analytics/goals: per-goal completions and per-source split, with the attribution disclosure (within-visit model, one completion per goal per visit, prospective counting from goal creation). Goal names are customer-authored data; use the stable numeric id t…- +17 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
UI5 MCP Server
{
"mcpServers": {
"mcp-server-80": {
"command": "npx",
"args": [
"-y",
"@ui5/mcp-server"
]
}
}
}
PromptEden
{
"mcpServers": {
"prompteden": {
"command": "npx",
"args": [
"-y",
"@prompteden/mcp-server"
],
"env": {
"PROMPTEDEN_API_KEY": "YOUR_PROMPTEDEN_API_KEY_HERE",
"PROMPTEDEN_BASE_URL": "YOUR_PROMPTEDEN_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
UI5 MCP Server is categorized under Developer Tools and uses a local stdio subprocess. PromptEden belongs to Developer Tools and uses a local stdio subprocess. Pick UI5 MCP Server for developer tools work and PromptEden for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
UI5 MCP Server is listed as free. Auth: no auth required. PromptEden is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-server-80 and prompteden as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, UI5 MCP Server has a quality signal of 68/100 (Great) with 2 views, 0 installs and 103 GitHub stars. PromptEden has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.