Skip to main content
Glama
Retio-ai

PageMap

Official
by Retio-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to PageMap

No user-submitted related servers found.

    Related Servers

    • Charlotte

      Kazuki10527
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through compact, structured representations — page summaries, targeted element queries, and full detail on demand — instead of paying for a full accessibility-tree dump on every call. This cuts the token cost of reading content-heavy pages by up to ~140x while still supporting navigation, forms, clicks, screenshots, and session management.
      4 npm
      -

    • Charlotte

      moore44
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to browse and interact with web pages through compact, typed structural representations — landmarks, headings, interactive elements, and forms — served in three controllable detail levels instead of full accessibility-tree dumps. Agents can navigate, query for specific elements, fill forms, manage tabs and cookies, capture screenshots, and run audits while paying a fraction of the token cost.
      4 npm
      -

    • Charlotte

      denizkaramanlis35063
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse, navigate, and interact with web pages through structured, token-efficient page representations — returning compact orientations and targeted element queries instead of full accessibility-tree dumps.
      4 npm
      -

    • Charlotte

      Erik8174
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through a token-efficient, structured representation of each page rather than raw accessibility-tree dumps. Agents get compact page orientations, targeted element queries, and full interaction—clicking, typing, form filling, screenshots, and session management—while controlling how much detail is returned per call.
      4 npm
      MIT

    • BrowserBridge MCP

      johannschiffer
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to navigate headless web pages, extract token-efficient accessibility trees and clean text, and interact with elements via stable node identifiers. It reduces context usage by converting pages into compact AOM structures and supports clicking, form filling, and page status checks.
      6
      MIT

    • Browser MCP

      drisplabs
      A
      license
      A
      quality
      A
      maintenance
      Gives AI agents a compact, semantic interface to the browser, returning structured page snapshots with stable element IDs instead of raw DOM. Enables agents to navigate, interact, and extract information from web pages efficiently.
      26
      11 npm
      18
      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

    A4.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a distinctly different purpose: page state vs full map, screenshot, navigation (back, scroll), form filling vs single action, waiting, tab lifecycle, and batch map retrieval. There is no meaningful overlap that would cause an agent to select the wrong tool for a given operation.

    Naming Consistency4/5

    Tool names consistently use snake_case with action-first verbs (get_, take_, navigate_, scroll_, fill_, wait_, execute_, open_, switch_, list_, close_, batch_get_). The pattern is mostly verb_noun, with minor deviations like 'navigate_back' and 'wait_for' that are still predictable and readable.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range for a web automation server. Each tool is justified and non-redundant, covering page inspection, interaction, navigation, waiting, screenshot, tab management, and batch processing without excessive granularity.

    Completeness4/5

    The tool surface covers the core browsing lifecycle: get page data, interact, fill forms, wait, navigate back, scroll, take screenshots, manage tabs, and batch fetch. Minor gaps include lack of an explicit forward navigation or refresh, and navigation to a URL is implicitly done via get_page_map(url), but these are workable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources