What is the key difference between Mobilerun and ProAgentStore?

Mobilerun belongs to the Developer Tools category with local stdio execution, while ProAgentStore belongs to the Developer Tools category with local stdio execution.

How do I install Mobilerun or ProAgentStore in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Mobilerun and ProAgentStore free or paid?

Mobilerun operates under a Free / Open Source model (No auth required). ProAgentStore operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mobilerun lists 0 tools with 0 views and 0 GitHub stars. ProAgentStore lists 0 tools with 0 views and 1 GitHub stars.

Can I use both Mobilerun and ProAgentStore together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Mobilerun vs ProAgentStore

In-depth architectural comparison of the Mobilerun and ProAgentStore MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Mobilerun

Developer Tools · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

ProAgentStore

Developer Tools · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Mobilerun if you need specialized Developer Tools tools running via a local process. Choose ProAgentStore if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mobilerun when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Mobilerun Details

Choose ProAgentStore when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore ProAgentStore Details

Feature & Specification Comparison

Specification	M Mobilerun Developer Tools	ProAgentStore Developer Tools
Summary	Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.	MCP-first control plane for ProAgentStore agents and private instances.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Mobilerun Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

ProAgentStore Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Mobilerun Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mobilerun": {
      "command": "npx",
      "args": [
        "-y",
        "mobilerun"
      ]
    }
  }
}

ProAgentStore Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "proagentstore": {
      "command": "npx",
      "args": [
        "-y",
        "@proagentstore/cli"
      ]
    }
  }
}

Frequently Asked Questions

Mobilerun is categorized under Developer Tools and uses a local stdio subprocess. In contrast, ProAgentStore belongs to Developer Tools using local stdio subprocess. Select Mobilerun when you need capabilities focused on developer tools and ProAgentStore when you require tools for developer tools.

More alternatives to Mobilerun More alternatives to ProAgentStore Developer Tools category hub