A side-by-side look at the Agent Device and Mobdev 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.
Mobdev 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.
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.
Mobdev
No confirmed install command for Mobdev yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Agent Device is categorized under OS Automation and uses an install path we have not confirmed yet. Mobdev belongs to OS Automation and uses an install path we have not confirmed yet. Pick Agent Device for os automation work and Mobdev 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.
Agent Device has no declared pricing — check the project's own site. Mobdev 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 agent-device and mobdev as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Device has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 5,078 GitHub stars. Mobdev has 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.