Skip to main content
Glama

Related Servers

Alternatives to Theseus

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A server that enables AI assistants to control a browser through tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      This server provides browser automation capabilities using Playwright, allowing LLMs to interact with web pages through structured accessibility snapshots. It enables tasks like web navigation, form filling, and data extraction without the need for screenshots or vision-tuned models.
      8,154 npm
      4
      Apache 2.0
    • A
      license
      D
      quality
      D
      maintenance
      AI-driven browser automation server that implements the Model Context Protocol to enable natural language control of web browsers for tasks like navigation, form filling, and visual interaction.
      1
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for browser automation using Puppeteer that enables AI assistants to navigate web pages, interact with UI elements, and capture screenshots. It supports comprehensive web tasks including form filling, content extraction, and executing custom JavaScript within the browser context.
      2
      MIT
    • -
      license
      Not graded
      quality
      F
      maintenance
      This server provides cloud browser automation capabilities using Browserbase, Puppeteer, and Stagehand. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a cloud browser environment.
      1,489 npm
      3,397
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Browser automation MCP server using Pydoll, enabling agents to navigate, observe, and interact with web pages via tools like page navigation, element clicking, and screenshot capture.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target distinct actions (fill, submit, navigate, wait_for, screenshot, note, session_*), and inspect_error vs assert_state have clearly different roles. The main overlap is click vs click_index, which is mitigated by the description telling agents to prefer click_index.

    Naming Consistency3/5

    All names are snake_case and readable, but conventions are mixed: bare verbs (fill, submit, navigate, click, note), verb_noun (read_page, click_index, assert_state, inspect_error, wait_for), and noun_verb (session_start, session_end, session_status). Predictable enough to follow, but not a single pattern.

    Tool Count4/5

    Fifteen tools is at the upper bound but justified by a real browser-automation loop: session lifecycle, navigation, interaction, waiting, verification and telemetry. Only the click/click_index pair feels like redundancy rather than a distinct capability.

    Completeness3/5

    The session lifecycle and core act/observe/verify loop are covered end to end, so no dead ends on the happy path. However, form automation lacks dropdown/select handling, keyboard actions (Enter, Tab, Escape), scrolling, and navigation history, which are common needs on real pages.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues