Exa Websets MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXA_API_KEY | Yes | Your Exa API key from dashboard.exa.ai/api-keys |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_search_exaA | Search the web using Exa AI - performs real-time web searches and can scrape content from specific URLs. Supports configurable result counts and returns the content from the most relevant websites. |
| websets_managerC | Manage content websets, searches, and data enhancements using Exa's platform. This single tool handles creating websets of web content, searching within them, enhancing data with AI, and setting up notifications. Much simpler than using separate tools for each operation. |
| websets_guideB | Get helpful guidance, examples, and workflows for using Exa's content websets effectively. Learn how to create websets, search content, enhance data, and set up notifications with practical examples. |
| knowledge_graphD | Maintain an onboard knowledge graph of webset results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_mcp_assets | List all available MCP server capabilities including prompts, tools, and resources |
| webset_discovery | Discover and explore available websets |
| webset_status_check | Check status of async webset operations |
| webset_analysis_guide | Guide for analyzing completed websets |
| webhook_setup_guide | Configure webhooks for webset notifications |
| quick_start | Get started quickly with creating your first webset |
| enrichment_workflow | Workflow for enriching webset data |
| integration_process | Process for integrating a webset with external systems |
| horizontal_process | Process for analyzing multiple websets horizontally |
| webset_portal | Portal for webset management |
| iterative_intelligence | Research assistant for iterative webset improvement |
| marketing_orchestration | Competitor and brand monitoring orchestration |
| crm_orchestration | Lead discovery and account-based marketing orchestration |
| hiring_orchestration | Recruiter and job seeker hiring orchestration |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| websets://orchestrations/* |
TDQS
Scored across 4 tools
websets_manager is a catch-all that handles search, enhancement, and notifications, which overlaps with the dedicated web_search_exa and blurs the boundary between operations. websets_guide and knowledge_graph are more distinct, but agents may struggle to choose between the manager and the search tool for search-like tasks.
All names use lowercase snake_case, but there is no consistent verb_noun pattern: websets_manager, websets_guide, web_search_exa, and knowledge_graph mix object names, actions, and brand suffixes. The names are readable and somewhat grouped by the 'websets' prefix, but the convention is not uniform.
Four tools is a reasonable count for a focused MCP server. However, websets_manager appears to bundle several major operations into one tool, making the effective surface larger than the count suggests and slightly under-scoped.
The set covers the main webset lifecycle (create, search, enhance, notify) plus external web search and knowledge graph maintenance. Explicit update/delete or listing operations are not surfaced, though the 'manage' wording may include them, so there are only minor gaps.