Skip to main content
Glama
ORCHORDS

orchords-web-pilot

Official
by ORCHORDS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to orchords-web-pilot

No user-submitted related servers found.

    Related Servers

    • sa2web-mcp

      sa2web
      A
      license
      C
      quality
      D
      maintenance
      Exposes a remote browser as MCP tools via Playwright, enabling AI agents to navigate and interact with web pages through DOM snapshots, clicks, typing, and form operations.
      40
      9 npm
      14
      Apache 2.0

    • mcp-agent-playwright

      ChristofMilius
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to drive a real Playwright browser over MCP to navigate pages, read accessibility-tree snapshots, click, type, screenshot, and evaluate JavaScript, either in a managed browser or attached to a running Chromium-based browser via CDP.
      20
      1
      MIT

    • jev-browser

      tontoko
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.
      10
      Apache 2.0

    • agentic-browser-mcp

      q35888
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to automate a real Chrome browser via Playwright, supporting session sharing and tools for navigation, clicking, typing, and more.
      11
      2
      MIT
    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.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each browser_ tool serves a distinct, well-defined action—navigation, snapshot, click, type, fill, press, hover, drag, select, screenshot, evaluate, wait, console, network, and captcha solving. Even the text-entry tools (type vs. fill) are clearly differentiated by their descriptions, eliminating ambiguity.

    Naming Consistency5/5

    All tools consistently use the 'browser_' prefix followed by a descriptive verb (or verb+noun) in lowercase snake_case, such as browser_navigate, browser_screenshot, browser_captcha_solve. This uniform pattern makes the tool names predictable and easy to learn.

    Tool Count5/5

    With 15 tools, the set is appropriately scoped for a comprehensive browser automation server. Each tool covers a specific aspect of web interaction without being redundant or overwhelming, staying within the ideal range for a focused purpose.

    Completeness4/5

    The tool surface covers the full lifecycle of browser interactions: navigation, inspection, element actions, waiting, screenshotting, JavaScript execution, and special handling like captchas. Minor gaps like tab/multi-page management or dialog handling exist, but they are non-essential for most web-pilot tasks.

    Maintenance

    ActivityNo data
    ResponsivenessWithin a week

    Resources