Skip to main content
Glama
extensiondev

@extension.dev/mcp

by extensiondev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @extension.dev/mcp

No user-submitted related servers found.

    Related Servers

    • browser-mcp

      Tuanm
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes your Chrome/Edge browser as MCP tools for AI agents, enabling browser automation through a Chrome extension with 47 tools for navigation, interaction, page reading, and more.
      12 npm
      -

    • neuron-inspector

      conquext
      A
      license
      B
      quality
      B
      maintenance
      Turns Chrome into a local MCP server, giving AI agents 51 browser tools to inspect DOM, automate clicks, run JavaScript, audit security and accessibility, mock APIs, extract data, record demos, and more from any MCP client.
      92
      79 npm
      MIT

    • Chrome MCP Bridge

      randyrt
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.
      -

    • Chrome Extension MCP Bridge

      ivoglent
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control the Google Chrome browser through a Node.js WebSocket bridge and a dedicated browser extension. It provides tools for capturing screenshots, executing JavaScript, managing tabs, and extracting page content via the MCP protocol.
      2
      -
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.2/5.0

    Scored across 32 tools

    Disambiguation4/5

    There is heavy surface overlap between extension_build/extension_dev/extension_start/extension_preview_web and between extension_inspect/extension_dom_snapshot/extension_eval, but the descriptions explicitly delineate each (e.g. 'ONLY this tool pierces closed shadow roots', 'use extension_dom_snapshot to choose which tab'). An agent can generally pick correctly, though the sheer density of cross-references makes misselection plausible.

    Naming Consistency5/5

    Every tool uses the extension_ prefix with snake_case, and most follow a predictable verb or verb_noun shape (extension_build, extension_create, extension_release_promote, extension_manifest_validate). A few noun-only names (extension_templates, extension_browsers, extension_shares) are exceptions but consistent within their purpose.

    Tool Count3/5

    At 32 tools the set is heavy, exceeding the 25-tool 'too many' threshold, though the domain (full extension lifecycle: scaffold, build, dev, inspect, publish, store submit, auth, releases) is genuinely broad so most tools earn their place. It still leans toward being a lot of surface for an agent to navigate.

    Completeness5/5

    The surface covers the whole lifecycle: templating, scaffolding, build, dev/start/preview sessions, inspection, eval, storage, reload, stop, auth, workspace/project creation, publish, release promotion/status, store submission, manifest validation, diagnoses, and docs. No obvious dead ends or missing lifecycle operations.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources