Agent Device vs Terminator MCP Agent

A side-by-side look at the Agent Device and Terminator MCP Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agent Device logoAgent DeviceOS AutomationDiscovery router for the agent-device CLI. Exposes status, install guidance, version-matched help, prompts, and resources for iOS, Android, tvOS, macOS, and Linux automation workflows.52GoodAuth: no auth requiredTerminator MCP Agent logoTerminator MCP AgentOS AutomationDesktop GUI automation using accessibility APIs. Control Windows, macOS, and Linux applications without vision models or screenshots. Supports workflow recording, structured data extraction, and browser DOM inspection.53GoodAuth: no auth required

Verdict: choose Agent Device for os automation work; choose Terminator MCP Agent for os automation. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Agent Device logoChoose Agent Device when

  • You need dedicated capabilities in the OS Automation domain.
  • Its auth model fits you: No auth required.
Explore Agent Device

Terminator MCP Agent logoChoose Terminator MCP Agent when

  • You need dedicated capabilities in the OS Automation domain.
  • Its auth model fits you: No auth required.
Explore Terminator MCP Agent

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Device logoAgent DeviceTerminator MCP Agent logoTerminator MCP Agent
CategoryOS AutomationOS Automation
Quality signal52/100 · Good53/100 · Good
Install commandNot confirmed yetNot confirmed yet
Transport——
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5,0781,657
Directory activity 3 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Agent Device tools

No tool names declared yet. Check the project README from the listing page.

Terminator MCP Agent 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.

Terminator MCP Agent

No confirmed install command for Terminator MCP Agent 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. Terminator MCP Agent belongs to OS Automation and uses an install path we have not confirmed yet. Pick Agent Device for os automation work and Terminator MCP Agent 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 is listed as free. Auth: no auth required. Terminator MCP Agent 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 callstackincubator-agent-device and louis030195-terminator-mcp-agent 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 52/100 (Good) with 3 views, 0 installs and 5,078 GitHub stars. Terminator MCP Agent has 53/100 (Good) with 4 views, 0 installs and 1,657 GitHub stars.