Drengr vs Ghost in the Droid
A side-by-side look at the Drengr and Ghost in the Droid MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Drengr for os automation work as a local process; choose Ghost in the Droid 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 Drengr when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Choose Ghost in the Droid when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 40/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 380 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Drengr | View Ghost in the Droid |
Tools & capabilities
Drengr tools
No tool names declared yet. Check the project README from the listing page.
Ghost in the Droid 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.
Drengr
{
"mcpServers": {
"drengr": {
"command": "npx",
"args": [
"-y",
"drengr"
]
}
}
}
Ghost in the Droid
{
"mcpServers": {
"ghost-in-the-droid": {
"command": "uvx",
"args": [
"ghost-in-the-droid"
]
}
}
}
Frequently asked questions
Drengr is categorized under OS Automation and uses a local stdio subprocess. Ghost in the Droid belongs to OS Automation and uses a local stdio subprocess. Pick Drengr for os automation work and Ghost in the Droid 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.
Drengr has no declared pricing — check the project's own site. Ghost in the Droid 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 drengr and ghost-in-the-droid as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Drengr has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Ghost in the Droid has 44/100 (Fair) with 0 views, 0 installs and 380 GitHub stars.