Mobilerun vs Pastea
A side-by-side look at the Mobilerun and Pastea MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mobilerun for os automation work as a local process; choose Pastea 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?
Choose Mobilerun when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
Choose Pastea when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pastea_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 49/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9,746 | 0 |
| Directory activity | 7 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Mobilerun | View Pastea |
Tools & capabilities
Mobilerun tools
No tool names declared yet. Check the project README from the listing page.
Pastea tools 1
pastea_statusReports whether Pastea is reachable and connected on this Mac, and what to do if it is not.
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.
Mobilerun
{
"mcpServers": {
"mobilerun": {
"command": "uvx",
"args": [
"mobilerun"
]
}
}
}
Pastea
{
"mcpServers": {
"pastea": {
"command": "npx",
"args": [
"-y",
"@pastea/mcp"
]
}
}
}
Frequently asked questions
Mobilerun is categorized under OS Automation and uses a local stdio subprocess. Pastea belongs to OS Automation and uses a local stdio subprocess. Pick Mobilerun for os automation work and Pastea 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.
Mobilerun has no declared pricing — check the project's own site. Pastea 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 mobilerun and pastea as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mobilerun has a quality signal of 49/100 (Fair) with 7 views, 0 installs and 9,746 GitHub stars. Pastea has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.