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.
      14 npm
      -

    • neuron-inspector

      conquext
      A
      license
      B
      quality
      C
      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
      671 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
      C
      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
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 30 tools

    Disambiguation4/5

    Tools are highly differentiated with explicit cross-references (e.g., extension_dev vs extension_start, extension_inspect vs extension_dom_snapshot), but a few name pairs like extension_create vs extension_project_create and several dev-session inspection tools could cause misselection without careful reading.

    Naming Consistency4/5

    All tools share the extension_ prefix and snake_case, creating a clear family, but the internal structure mixes bare verbs (build, dev, start), verb-object (list_extensions, add_feature), object-verb (manifest_validate, release_promote), and nouns (templates, shares, browsers), so there is no single verb_noun pattern throughout.

    Tool Count4/5

    30 tools is high, but the toolset covers the full extension lifecycle from scaffolding and dev sessions through building, testing, previewing, publishing, releasing, and store submission; each tool addresses a distinct function, so the count feels scaled to the broad platform scope rather than padded.

    Completeness4/5

    The lifecycle is well covered: create, develop, test, build, preview, publish, promote, submit, and monitor, plus auth and browser management. Minor gaps exist such as no unpublish/demote or cancel-submission path, but agents can generally work around them.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources