Skip to main content
Glama
A1-x-Tech

mcp-google-custom-search

Related Servers

Alternatives to mcp-google-custom-search

No user-submitted related servers found.

    Related Servers

    • 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
    • F
      license
      B
      quality
      D
      maintenance
      Enables web search and content extraction using Google's search engine, with customizable parameters for result count, content type, time range, and domain filtering.
      2
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables web search capabilities through a remote smart search API with configurable result count, pagination, language, and safety filters, returning structured JSON results.
      -
    • 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
    • A
      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
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform Google searches across web, news, videos, images, shopping, and places, retrieve existing search results, and inspect account usage through stdio using compact text summaries or structured JSON.
      80 npm
      MIT

    TDQS

    A4.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    search and search_images are clearly separated by result type, and raw_request is explicitly an escape hatch for raw API access. There is no plausible confusion between these three tools.

    Naming Consistency4/5

    search and search_images follow a clear verb_noun pattern with consistent lowercase snake_case. raw_request breaks that pattern slightly, but it is a conventional escape-hatch name and not confusing.

    Tool Count5/5

    Three tools are well-scoped for the Google Custom Search JSON API: web search, image search, and a raw request fallback. Each tool earns its place without redundancy or unnecessary bloat.

    Completeness5/5

    The tool set fully covers the API's read-only capabilities: standard web search, image search, pagination, filters, and every remaining parameter via raw_request. There are no meaningful gaps, and no CRUD is needed since the API only supports GET.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues