A side-by-side look at the Ghost in the Droid and Mirroir MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ghost in the Droid for os automation work as a local process; choose Mirroir MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ghost in the Droid when
You need dedicated capabilities in the OS Automation domain.
No tool names declared yet. Check the project README from the listing page.
Mirroir MCP tools
No tool names declared yet. Check the project README from 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.
Ghost in the Droid is categorized under OS Automation and uses a local stdio subprocess. Mirroir MCP belongs to OS Automation and uses a local stdio subprocess. Pick Ghost in the Droid for os automation work and Mirroir MCP for os automation.
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.
Ghost in the Droid has no declared pricing — check the project's own site. Mirroir MCP 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 ghost-in-the-droid and mirroir-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ghost in the Droid has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 380 GitHub stars. Mirroir MCP has 51/100 (Good) with 1 views, 0 installs and 256 GitHub stars.