Pastea vs Mobilerun

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

Pastea logoPasteaOS Automation · Local subprocess (stdio)Search, read and re-copy your Mac clipboard history from Pastea. Local, pairs with one click.55GoodAuth: not declaredMobilerun logoMobilerunOS Automation · Local subprocess (stdio)Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows.49FairAuth: not declared

Verdict: choose Pastea for os automation work as a local process; 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?

Pastea logoChoose Pastea when

  • You need dedicated capabilities in the OS Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like pastea_status.
Explore Pastea

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.

SpecPastea logoPasteaMobilerun logoMobilerun
CategoryOS AutomationOS Automation
Quality signal55/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars09,746
Directory activity 1 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools1Not listed

Tools & capabilities

Pastea tools 1

  • pastea_statusReports whether Pastea is reachable and connected on this Mac, and what to do if it is not.

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.

Pastea

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pastea": {
      "command": "npx",
      "args": [
        "-y",
        "@pastea/mcp"
      ]
    }
  }
}

Mobilerun

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

Frequently asked questions

Pastea is categorized under OS Automation and uses a local stdio subprocess. Mobilerun belongs to OS Automation and uses a local stdio subprocess. Pick Pastea 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.

Pastea has no declared pricing — check the project's own site. 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 pastea and mobilerun as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Pastea has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Mobilerun has 49/100 (Fair) with 7 views, 0 installs and 9,746 GitHub stars.