What is the key difference between Tempo and Agent Browser?

Tempo belongs to the Developer Tools category with local stdio execution, while Agent Browser belongs to the Developer Tools category with local stdio execution.

How do I install Tempo or Agent Browser 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 Tempo and Agent Browser free or paid?

Tempo operates under a Free / Open Source model (No auth required). Agent Browser operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Tempo lists 11 tools with 0 views and 0 GitHub stars. Agent Browser lists 0 tools with 0 views and 4 GitHub stars.

Can I use both Tempo and Agent Browser 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

Tempo vs Agent Browser

In-depth architectural comparison of the Tempo and Agent Browser 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

Tempo

Developer Tools · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Agent Browser

Developer Tools · Local stdio

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

Verdict Summary: Choose Tempo if you need specialized Developer Tools tools running via a local process. Choose Agent Browser 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 Tempo 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: log_checkin, ingest_revenue_event, ingest_calendar_event.

Explore Tempo Details

Choose Agent Browser 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 Agent Browser Details

Feature & Specification Comparison

Specification	T Tempo Developer Tools	A Agent Browser Developer Tools
Summary
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Tempo Tools (11)

log_checkin

Log mood / energy / stress / sleep

ingest_revenue_event

Record revenue (from Stripe connector or manual)

ingest_calendar_event

Record a calendar block (internal, sales, deep work)

tempo_score

Compute the composite Tempo score + RpRH

recommend_actions

Prescriptive business moves based on current state

apply_action

Log (or, on Pro, execute) an action

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

Tempo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tempo": {
      "command": "uvx",
      "args": [
        "tempo-mcp"
      ]
    }
  }
}

Agent Browser Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agent-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aether-browser"
      ]
    }
  }
}

Frequently Asked Questions

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