MCP Installer vs Legwork
A side-by-side look at the MCP Installer and Legwork MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Installer for developer tools work as a local process; choose Legwork for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Installer 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
install_repo_mcp_server, install_local_mcp_server.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 63/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
MCP Installer tools 2
install_repo_mcp_serverInstall an MCP server via npx or uvxinstall_local_mcp_serverInstall an MCP server whose code is cloned locally on your computer
Legwork tools 12
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.
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.
MCP Installer
{
"mcpServers": {
"anaisbetts-mcp-installer": {
"command": "npx",
"args": [
"@anaisbetts/mcp-installer"
]
}
}
}
Legwork
{
"mcpServers": {
"legwork": {
"url": "https://heylegwork.com/mcp"
}
}
}
Frequently asked questions
MCP Installer is categorized under Developer Tools and uses a local stdio subprocess. Legwork belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick MCP Installer for developer tools work and Legwork 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.
MCP Installer is listed as free. Auth: no auth required. Legwork has no declared pricing — check the project's own site. 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 anaisbetts-mcp-installer and legwork as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Installer has a quality signal of 63/100 (Good) with 3 views, 0 installs and 1,532 GitHub stars. Legwork has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.