Skip to main content
Glama
geezerrrr

Exa MCP Server

by geezerrrr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Exa MCP Server

No user-submitted related servers found.

    Related Servers

    • Exa MCP Server

      MrunmayS
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to perform real-time web searches using the Exa AI Search API in a safe and controlled manner.
      2
      22,768 npm
      -

    • Exa MCP Server

      theishangoswami
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants like Claude to perform web searches using the Exa AI Search API, providing real-time structured search results.
      1
      6
      -

    • MCP Web Research Server

      jevy
      A
      license
      B
      quality
      D
      maintenance
      A server that integrates with Claude Desktop to enable real-time web research capabilities, allowing users to search Google, extract webpage content, and capture screenshots directly from conversations.
      3
      999 npm
      MIT

    • Exa MCP Server

      exa-labs
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
      8
      22,768 npm
      5,048
      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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_code_context_exa is specialized for programming-related searches with high-quality code context, while web_search_exa is a general web search tool for broader queries. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the query content.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern: they use snake_case and start with a verb (get, search) followed by a noun (code_context, web). The pattern is uniform across the set, with no deviations in style or structure.

    Tool Count3/5

    With only 2 tools, the server feels thin for a general-purpose search domain, as it might lack coverage for intermediate or specialized tasks beyond code and web searches. However, the tools are well-defined, so it's borderline but not severely mismatched.

    Completeness3/5

    The server covers two key search domains (code and web), but there are notable gaps: it lacks tools for other common search types (e.g., image, news, academic) or advanced operations like filtering or saving results. This could limit agent effectiveness in broader search scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources