Back to Gap Map Organization

AgentDesk

company

Scores

1 product on the map — 1 open.

BrowserTools MCP

Openness

5 high confidence
5.0
license
MIT (OSI)
source
public
core features withheld
no — the MCP server and the Chrome extension both ship in the MIT repository; AgentDesk's only other product, AgentDesk Studio, is a separate waitlisted app

BrowserTools MCP is MIT-licensed, and both halves of it, the server and the Chrome extension, are in the public repository and run from there. AgentDesk sells no edition of it; the only other product its site names is a separate app still on a waitlist.

Adoption

2 medium confidence
2.0

Adoption is the trailing month of npm downloads of @agentdeskai/browser-tools-mcp, the package the README's MCP configuration runs through npx. The Chrome extension is loaded unpacked from the repository, so nothing counts it.

Capability

3 medium confidence
3.0

BrowserTools MCP works on one system, the user's browser, and brings no credentials of its own: it reads the session the user is already signed into, and its connector runs on the user's machine. That puts it level with Playwright MCP, which drives a fresh browser instead; neither manages logins nor hosts anything.

  • https://raw.githubusercontent.com/AgentDeskAI/browser-tools-mcp/main/README.md recorded 2026-11-12

    The README's tool table lists getConsoleLogs, getNetworkLogs, getSelectedElement, listTabs, navigateTab, softClick / softType, takeScreenshot, getBrowserStorage and four Lighthouse audits. The connector "binds `127.0.0.1` and refuses non-loopback addresses", the HTTP API "requires a per-run bearer token", and "Credentials are scrubbed on the way in".