AgentPhone vs BrowserTap MCP

In-depth architectural comparison of the AgentPhone and BrowserTap MCP 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.

Which MCP Server Should You Choose?

Choose AgentPhone 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 AgentPhone Details

B

Choose BrowserTap MCP 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).
• Primary tools included: get_setup_status, get_automation_profile, set_automation_profile.

Explore BrowserTap MCP Details

Feature & Specification Comparison

Specification	AgentPhone Developer Tools	B BrowserTap MCP Developer Tools
Summary	Give AI agents real phone numbers, messages, and voice calls via MCP.	MCP server that drives the real Chrome you already use, through an extension and CDP.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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

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

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

Related MCP Server Comparisons