Skip to main content
Glama
cmann50

MCP Chrome Google Search

by cmann50
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to MCP Chrome Google Search

No user-submitted related servers found.

    Related Servers

    • chrome-bridge

      bbauersjt
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides a direct bridge between Claude and an authenticated Chrome session, enabling fetch requests with session cookies and JavaScript execution within live web pages.
      -

    • Web Search MCP

      pranavms13
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables web searching through Google, DuckDuckGo, and Bing using a headless Chrome browser, returning structured results with titles, URLs, and snippets. Also supports fetching and extracting text content from any webpage.
      13
      MIT

    • chrome-mcp

      Mehmoodqureshi
      A
      license
      C
      quality
      A
      maintenance
      Enables controlling a real Chrome browser from MCP hosts like Claude, with extension-based or CDP fallback, supporting tabs, navigation, interaction, and page reading tools.
      39
      197 npm
      6
      MIT

    • familiar-mcp

      dominion525
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that drives the user's real signed-in Chrome on macOS via AppleScript (Apple Events). 32 tools covering tab/window control, navigation, DOM extraction, form interaction, and arbitrary JS execution. Same engine as the familiar Claude Code skill in the repository.
      MIT

    • Chrome MCP Server

      marie6789040106650
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms Chrome browser into an AI-controlled automation tool that allows AI assistants like Claude to access browser functionality, enabling complex automation, content analysis, and semantic search while preserving your existing browser environment.
      MIT
    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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: web_fetch extracts content from a specific webpage, while web_search performs web searches and returns result pages. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.

    Naming Consistency5/5

    Both tool names follow a consistent snake_case pattern with a clear verb-noun structure: web_fetch and web_search. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count2/5

    With only 2 tools, the server feels thin for a Google Search domain, which typically involves more operations like advanced filtering, image search, or history management. While the tools cover basic fetch and search, the scope is limited and could benefit from additional functionality to fully represent the domain.

    Completeness3/5

    The tools cover core search and content extraction, but there are notable gaps for a Google Search server, such as no tools for image search, news search, or handling search settings. Agents can perform basic tasks but may encounter dead ends for more advanced operations, indicating incomplete coverage of the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources