Log inSubmit server

Terminator MCP Agent vs Mobilerun

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

Terminator 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 requiredMobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.48FairAuth: not declared

Verdict: choose Terminator MCP Agent for os automation work; choose Mobilerun 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?

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

Mobilerun logoChoose Mobilerun when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Mobilerun

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTerminator MCP Agent logoTerminator MCP AgentMobilerun logoMobilerun
CategoryOS AutomationOS Automation
Quality signal53/100 · Good48/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,6579,709
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Terminator MCP Agent View Mobilerun

Tools & capabilities

Terminator MCP Agent tools

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

Mobilerun 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.

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.

Mobilerun

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mobilerun": {
      "command": "uvx",
      "args": [
        "mobilerun"
      ]
    }
  }
}

Frequently asked questions

Terminator MCP Agent is categorized under OS Automation and uses an install path we have not confirmed yet. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick Terminator MCP Agent for os automation work and Mobilerun 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. Terminator MCP Agent has no confirmed install command yet — follow its own setup instructions.

Terminator MCP Agent is listed as free. Auth: no auth required. Mobilerun 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 louis030195-terminator-mcp-agent and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Terminator MCP Agent has a quality signal of 53/100 (Good) with 4 views, 0 installs and 1,657 GitHub stars. Mobilerun has 48/100 (Fair) with 2 views, 0 installs and 9,709 GitHub stars.

Popular comparisons with Terminator MCP Agent

Popular comparisons with Mobilerun