Legwork vs UI5 MCP Server — MCP Server Comparison | AllMCPs
Legwork vs UI5 MCP Server
A side-by-side look at the Legwork 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 Legwork for developer tools work over a hosted endpoint; 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 Legwork when
You need dedicated capabilities in the Developer Tools domain.
You prefer a remote HTTP/SSE transport.
You want tools like octopus_register, octopus_declare_intents, octopus_marketplace.
octopus_registerCreate an Octopus agent account. Instant, returns an api_key (SAVE IT somewhere durable: .env, project memory). In the private beta your first $25 of platform fees are waived. Do this once per project, not per session.
octopus_declare_intentsPre-register the kinds of tasks you expect to post (category, description, locations, cadence). Workers get recruited for your categories first and you get priority access as supply arrives; first declaration in the beta adds $10 fee credit.
octopus_marketplaceLive Octopus marketplace stats and recent open tasks. No auth needed.
octopus_post_taskHire a human: post a paid task to Octopus. The budget (USD) goes entirely to the worker and is escrowed from your credits along with a 15% platform fee (waived while your beta fee credit lasts), released when you approve the work. Write acceptance criteria as individually verifiable checks, the human answers each one with evidence. Humans take minutes-to-hours: post early, keep working, then poll with octopus_get_task.
octopus_my_tasksList the tasks you have posted, with statuses. Tasks with status "submitted" need your review.
octopus_get_taskFetch one of your tasks: status, submissions with per-criterion evidence and attachment URLs, message thread, and an advice field with the sensible next move. Set wait_seconds (max 55) to block until the status moves on or a new message arrives, pass since_status/since_messages from your last look.
octopus_send_messageReply on a task's thread, the human working your task can ask clarifying questions; answer promptly or the work stalls.
octopus_approveAccept submitted work: releases the escrowed budget to the human and completes the task. Verify each criterion response (and open attachment URLs) first.
octopus_request_changesSend submitted work back for revision with specific, per-criterion feedback. The human revises and resubmits.
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.
Legwork is categorized under Developer Tools and uses a remote HTTP/SSE transport. UI5 MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Legwork 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.
Legwork has no declared pricing — check the project's own site. 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 legwork and mcp-server-80 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Legwork has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. UI5 MCP Server has 68/100 (Great) with 2 views, 0 installs and 103 GitHub stars.
octopus_cancel_taskCancel a task for a full refund. Allowed while open, or while claimed-and-overdue.
octopus_walletYour credit balance and ledger. To add credits: octopus_topup.
octopus_topupCreate a payment link to add credits (returns a Stripe Checkout URL to hand to your principal). In sandbox mode this explains the sandbox instead.
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 symbols
get_project_infoGet general information about a local UI5 project.
create_ui5_appCreate a new basic SAPUI5 application implemented in TypeScript or JavaScript
get_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 Card
run_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.