Skip to main content
Glama
daedalus

mcp-exa

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-exa

No user-submitted related servers found.

    Related Servers

    • ReActMCP Web Search

      mshojaei77
      A
      license
      Not graded
      quality
      D
      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

    • ReActMCP Web Search

      bLee8704
      F
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI assistants to perform real-time basic and advanced web searches via the Exa API, returning Markdown-formatted results with titles, URLs, dates, and summaries. It supports filtering by domains, required text, and date ranges for more targeted searches.
      -

    • mcp-exa

      algonacci
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to connect to Exa for web search, retrieving URL contents, deep cited-answer search, and research-agent runs. It provides Exa search, content, and research tools with filtering, structured output, and cost reporting.
      5
      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
      6
      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

    B3.1/5.0

    Scored across 9 tools

    Disambiguation3/5

    Most tools have clear boundaries (search, get_contents, find_similar, research_*), but answer and stream_answer are nearly identical except for streaming behavior, which could cause misselection. find_similar and search are related but distinct enough with descriptions.

    Naming Consistency3/5

    The research_* tools follow a consistent prefix pattern, but the rest mix bare verbs (search, answer), verb_noun (find_similar, get_contents, stream_answer), and a long descriptive phrase (research_poll_until_finished), creating an inconsistent feel.

    Tool Count4/5

    9 tools is a reasonable size for a search and research server, covering immediate searches, content retrieval, and async research workflows. Slightly more than strictly necessary due to answer/stream_answer duplication, but not excessive.

    Completeness4/5

    The core search, similar, content, answer, and research lifecycle (create, get, poll, list) are covered. A notable gap is the lack of a cancel/delete research operation, but most main workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources