Skip to main content
Glama
x15907982411

exa-mcp-server-for-operit

by x15907982411
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to exa-mcp-server-for-operit

No user-submitted related servers found.

    Related Servers

    • mcp-exa

      daedalus
      A
      license
      B
      quality
      C
      maintenance
      Exposes the Exa web search API as an MCP server, providing tools for web searching, content retrieval, and similar page discovery. It also supports advanced features like AI-generated answers and automated research task management.
      9
      MIT

    • ReActMCP Web Search

      mshojaei77
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that integrates real-time web search capabilities into AI assistants using the Exa API, providing both basic and advanced search functionality with formatted markdown results.
      143
      MIT

    • io.github.VelvetSP/web

      VelvetSP
      A
      license
      A
      quality
      C
      maintenance
      An open-source MCP server providing AI agents with neural web search via Exa and tiered web fetch (Exa, local browser, Firecrawl) as a drop-in replacement for built-in web tools, preserving provenance and guarding against SSRF.
      6
      1
      MIT

    • 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
      79,339 npm
      -
    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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    web_search_exa and web_fetch_exa have clearly distinct purposes: one searches the web and returns highlights, the other fetches full page content. There is no overlap in functionality, and their complementary nature is explicitly described.

    Naming Consistency5/5

    Both tools follow the same verb_noun pattern with a consistent shared prefix: web_search_exa and web_fetch_exa. The naming is predictable and reflects the action each tool performs.

    Tool Count4/5

    Two tools is minimal but appropriate for a server focused on web search and retrieval. The pair forms a complete workflow (search then fetch), and adding more tools for a simple utility like this could be overkill. The count feels slightly thin but not insufficient for the stated purpose.

    Completeness4/5

    The server covers the core lifecycle of web content retrieval: searching for relevant pages and fetching full content from known URLs. Minor gaps exist, such as no findSimilar or advanced filtering, but the essential use case is fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources