Skip to main content
Glama
Richard-Weiss

Google Custom Search Engine MCP Server

by Richard-Weiss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Google Custom Search Engine MCP Server

No user-submitted related servers found.

    Related Servers

    • Web Search MCP Server

      Mantraa-Zzz
      F
      license
      B
      quality
      D
      maintenance
      Enables web searching and content scraping through Google Custom Search API. Provides tools to search the internet, extract webpage content, and automatically scrape search results for comprehensive information gathering.
      3
      -

    • Google Search MCP Server

      jspv
      A
      license
      A
      quality
      D
      maintenance
      Enables users to perform Google Custom Search queries through the Model Context Protocol. Requires Google API credentials and Custom Search Engine configuration for web search functionality.
      1
      MIT

    • Google Search MCP Server

      Calandrel
      A
      license
      B
      quality
      D
      maintenance
      Enables performing Google searches using the Custom Search Engine API with support for various parameters like date restriction, site search, and file type. Returns search results in a conversational format.
      1
      Apache 2.0

    • Web Search MCP Server

      williamvd4
      A
      license
      B
      quality
      D
      maintenance
      Enables free web searching using Google search results with no API keys required, returning structured results with titles, URLs, and descriptions.
      1
      31 npm
      5
      MIT
    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

    A3.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'google_search' has a clearly defined and distinct purpose for searching the custom search engine.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'google_search' follows a clear and appropriate verb_noun pattern that would be consistent if more tools existed.

    Tool Count2/5

    A single tool is too few for a server that implies broader functionality, such as a search engine with potential follow-up actions. The description mentions using links in follow-up requests with different tools, suggesting gaps that a single tool cannot cover, making the count inappropriate for the apparent scope.

    Completeness2/5

    The server is severely incomplete for a search engine domain. While the core search functionality is present, the description hints at missing tools for follow-up actions like fetching full content from links, and there are no tools for managing searches, filters, or other related operations, leading to significant gaps that will cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources