Localhost MCP vs UI5 MCP Server
A side-by-side look at the Localhost MCP and UI5 MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Localhost MCP for developer tools work as a local process; choose UI5 MCP Server 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 Localhost MCP 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
list_dev_servers, port_info, kill_server.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 59/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 103 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 5 | 10 |
| Full listing | View Localhost MCP | View UI5 MCP Server |
Tools & capabilities
Localhost MCP tools 5
list_dev_serversRead-only. Lists every local development server (next, vite, nuxt, remix, astro, rails, django, flask, express, deno, bun, etc.) currently LISTENING on a TCP port. For each: port, pid, process name, command line, working directory, project name, detected framework, uptime, memory (MB), CPU %, and owning user. Uses `lsof` on macOS/Linux and `netstat` on Windows; on Windows the cwd/framework fields are limited. Takes no arguments. Returns `{ count, servers[] }`.port_infoRead-only. Inspects a single TCP port and reports the dev server holding it (same fields as `list_dev_servers`). If nothing is listening, or the listener is not a recognised dev process, returns `{ port, status: "free" }`. Useful for answering "what's on :3000?" before starting or killing something.kill_serverTerminates a local dev server by `pid` or `port`. DESTRUCTIVE. Safe by default: with no `confirm`, this is a DRY RUN — it reports what it would kill and changes nothing. Pass `confirm: true` to actually terminate: sends SIGTERM, waits up to 5s, then escalates to SIGKILL (or SIGKILL immediately if `force: true`). Refuses PIDs below 1000 and processes that don't look like dev servers. Provide exactly one of `pid` or `port`. Returns what was (or would be) killed and the signal used.find_zombiesRead-only. Flags dev servers that look abandoned — all three of: uptime > 6h AND CPU < 1% AND memory > 100MB. By default it excludes known always-on noise (VS Code server, language servers, other MCP servers, postgres/redis, sidekiq, etc.); set `include_excluded: true` to also list those. Each candidate comes with the reasons it matched. This tool never kills anything — pass results to `kill_server`. Returns `{ count, candidates[] }`.port_conflictRead-only. Diagnoses an `EADDRINUSE` situation: given a port, returns the dev server currently blocking it plus 5 free alternative ports nearby. Use it when a `listen EADDRINUSE` error fires and you want both the culprit and a port to switch to.
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.
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.
Localhost MCP
{
"mcpServers": {
"hasanjahidul-localhost-mcp": {
"command": "npx",
"args": [
"-y",
"localhost-mcp"
]
}
}
}
UI5 MCP Server
{
"mcpServers": {
"mcp-server-80": {
"command": "npx",
"args": [
"-y",
"@ui5/mcp-server"
]
}
}
}
Frequently asked questions
Localhost MCP is categorized under Developer Tools and uses a local stdio subprocess. UI5 MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Localhost MCP for developer tools work and UI5 MCP Server 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.
Localhost MCP is listed as free. Auth: no auth required. UI5 MCP Server is listed as free. Auth: no auth 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 hasanjahidul-localhost-mcp and mcp-server-80 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Localhost MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 4 GitHub stars. UI5 MCP Server has 68/100 (Great) with 3 views, 0 installs and 103 GitHub stars.