A side-by-side look at the Looktap MCP and AutoMobile MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Looktap MCP for os automation work as a local process; choose AutoMobile 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?
L
Choose Looktap MCP when
You need dedicated capabilities in the OS Automation domain.
No tool names declared yet. Check the project README from the listing page.
AutoMobile 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.
Looktap MCP is categorized under OS Automation and uses a local stdio subprocess. AutoMobile belongs to OS Automation and uses a local stdio subprocess. Pick Looktap MCP for os automation work and AutoMobile 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.
Looktap MCP has no declared pricing — check the project's own site. AutoMobile 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 looktap-mcp and automobile as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Looktap MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 3 GitHub stars. AutoMobile has 49/100 (Fair) with 3 views, 0 installs and 52 GitHub stars.