Skip to main content
Glama
x15907982411

exa-mcp-server-for-operit

by x15907982411
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EXA_API_KEYYesYour Exa API key. Obtain from https://dashboard.exa.ai/api-keys
EXA_TOOL_ENABLESNoComma-separated list of tool names to enable, e.g., "web_search_exa,web_fetch_exa". Additional advanced tools can be enabled by appending their names.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
web_search_exaA

Search the web for any topic and get clean, ready-to-use content.

  Best for: Finding current information, news, facts, people, companies, or answering questions about any topic.
  Returns: Clean text content from top search results.

  Query tips:
  describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
  Use category:people / category:company to search through Linkedin profiles / companies respectively.
  If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
web_fetch_exaA

Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL.

Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).

Prompts

Interactive templates invoked by user choice

NameDescription
web_search_helpGet help with web search using Exa

Resources

Contextual data attached and managed by the client

NameDescription
tools_listList of available Exa tools and their descriptions
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