Skip to main content
Glama
Moha2005269

agentgo-mcp

by Moha2005269
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to agentgo-mcp

No user-submitted related servers found.

    Related Servers

    • browser-mcp

      huaka1
      A
      license
      A
      quality
      D
      maintenance
      Agent-native browser control MCP server that enables AI agents to browse and interact with web pages via accessibility tree snapshots and ref ID-based commands.
      15
      2
      MIT

    • Ghostlight

      sylin-org
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.
      25
      1
      Apache 2.0

    • agentgo

      Moha2005269
      F
      license
      Not graded
      quality
      A
      maintenance
      A real Chromium browser for AI agents, driven over MCP: compact page outlines with stable refs, diff-only replies after each action, real mouse and keyboard input, the agent's own signed-in accounts, and human approval for payments. Windows 11.
      2
      -

    • mcp-server-agent-browser

      codeChap
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps agent-browser to let LLMs control a real browser, providing tools for navigation, interaction, reading page content, accessibility snapshots, screenshots, and session management.
      1
      -

    • browser-use-relay-mcp

      mlnima
      F
      license
      A
      quality
      B
      maintenance
      An MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.
      8
      -
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool targets a distinct phase of browser work (open, read, act, batch, wait, tabs, screenshot, human handoff, guide, account, generic call), so an agent can generally pick correctly. The only mild overlaps are browser_wait vs browser_wait_human (same 'wait' verb, different targets) and browser_call vs browser_act (generic protocol escape hatch can duplicate specific tools).

    Naming Consistency5/5

    All tools share a strict browser_ prefix in snake_case, giving a fully predictable pattern. The verb/noun mix (browser_tabs, browser_account) is consistent across the set and reads naturally.

    Tool Count5/5

    11 tools is well-scoped for a browser automation server, with each tool earning its place: load, read, act, batch, wait, tabs, screenshot, human handoff, guide, accounts, and a generic escape hatch. Nothing feels redundant or missing from a count perspective.

    Completeness4/5

    The surface covers the full browse lifecycle: navigation, reading multiple views, acting, batching, waiting, tab management, screenshots, human handoff, and account/API access, plus browser_call as a catch-all for uncovered protocol methods. Minor gaps include no explicit session/close lifecycle tool, but those are reachable via browser_call.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources