A side-by-side look at the Azdroid and Agent Device MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Agent Device 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.
Azdroid
No confirmed install command for Azdroid yet — follow the setup steps linked from its listing page rather than a guessed package name.
Agent Device
No confirmed install command for Agent Device yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Azdroid is categorized under OS Automation and uses an install path we have not confirmed yet. Agent Device belongs to OS Automation and uses an install path we have not confirmed yet. Pick Azdroid for os automation work and Agent Device for os automation.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Azdroid is listed as free. Auth: no auth required. Agent Device 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 azdroid and callstackincubator-agent-device as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Azdroid has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Agent Device has 52/100 (Good) with 3 views, 0 installs and 5,078 GitHub stars.