Skip to main content
Glama
Sophomoresty

gemini-search-mcp

by Sophomoresty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gemini-search-mcp

No user-submitted related servers found.

    Related Servers

    • gemini-search-mcp

      mkih76
      A
      license
      A
      quality
      D
      maintenance
      Free, unlimited web search MCP server powered by Google AI Mode (Gemini) without API key. Provides real-time search results for AI agents like Claude, Cursor, and Windsurf.
      2
      MIT

    • gemini-search-mcp

      Lambda-zhou
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for web search powered by Google AI Mode (Gemini). Free, unlimited, no API key.
      MIT

    • gemini-search

      leacvikas0
      A
      license
      A
      quality
      D
      maintenance
      Free, unlimited web search MCP server using Gemini CLI's Google Search grounding to provide cited, live web results for any AI agent.
      3
      1
      MIT

    • Gemini Google Web Search MCP

      louxsye
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables AI models to perform Google Web searches using the Gemini API, complete with citations and grounding metadata for accurate information retrieval. It is compatible with Claude Desktop and other MCP clients for real-time web access.
      1
      3
      Apache 2.0

    • evo-scry

      krich11
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for internet search via direct Google and DuckDuckGo HTML scraping with AI-powered result normalization and optional summarization, requiring no API keys for search.
      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

    A4.1/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have distinct intentions: 'ask' for general questions that may use training data, and 'web_search' for explicit web-grounded answers. The description of 'ask' clarifies it is similar but flexible, reducing ambiguity. However, an agent might still be uncertain which to choose when a question could be answered from either source.

    Naming Consistency3/5

    'ask' is a single verb, while 'web_search' is verb_noun with underscore. They do not follow a consistent pattern, which could be slightly confusing. However, both names are descriptive and readable.

    Tool Count3/5

    With only 2 tools, the server feels thin for a search/QA domain. Typically a well-scoped server has 3-15 tools. However, for a specialized server focused on Google AI Mode, two tools (one for general questions and one for web search) might suffice, but it's on the lower end of acceptable.

    Completeness3/5

    The server covers two modes of AI-powered answering, but lacks a tool for pure training-data answers without web search, as 'ask' may still use web search. Users cannot force offline-only answers. Additionally, there is no tool for raw search results, only synthesized answers. This leaves notable gaps for a comprehensive search toolset.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources