Back to the MCP Gateway catalog

MCP Gateway · Catalog

Exa icon

Exa MCP server

Official

Exa MCP is the official Model Context Protocol server for Exa, with tools that let agents run web searches, crawl pages, research companies and people, and pull code context. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

AI & search8 toolsAuth: open

Behind the MCP Gateway

Run Exa MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Exa call inspected and logged.

Deploy on MCP Gateway

Tools · 8

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

web_search_exa

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, ready for LLM use. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people to specifically search through Linkedin profiles and category:company to search through company pages. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

company_research_exa

[Deprecated: Use web_search_advanced_exa instead] Research any company to get business information, news, and insights. Best for: Learning about a company's products, services, recent news, or industry position. Returns: Company information from trusted business sources.

crawling_exa

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).

people_search_exa

[Deprecated: Use web_search_advanced_exa instead] Find people and their professional profiles. Best for: Finding professionals, executives, or anyone with a public profile. Returns: Profile information and links.

linkedin_search_exa

⚠️ DEPRECATED: This tool is deprecated. Please use 'people_search_exa' instead. This tool will be removed in a future version. For now, it searches for people on LinkedIn using Exa AI - finds professional profiles and people.

deep_researcher_start

[Deprecated] Start an AI research agent that searches, reads, and writes a detailed report. Takes 15 seconds to 2 minutes. Best for: Complex research questions needing deep analysis and synthesis. Returns: Research ID - use deep_researcher_check to get results. Important: Call deep_researcher_check with the returned research ID to get the report.

deep_researcher_check

[Deprecated] Check status and get results from a deep research task. Best for: Getting the research report after calling deep_researcher_start. Returns: Research report when complete, or status update if still running. Important: Keep calling with the same research ID until status is 'completed'.

get_code_context_exa

Find code examples, documentation, and programming solutions. Best for: Any programming question - API usage, library examples, code snippets, debugging help. Returns: Relevant code and documentation. Query tips: describe what you're looking for specifically. "Python requests library POST with JSON body" not "python http". If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

Questions

What is an Exa MCP server?
An Exa MCP server exposes Exa to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as web_search_exa or company_research_exa to work with Exa. The server in this catalog is the official Exa MCP server.
What can you do with Exa MCP?
Agents can run web searches, crawl pages, research companies and people, and pull code context. The catalog lists 8 tools for this server, including web_search_exa, company_research_exa, and crawling_exa. The full list with descriptions is on this page.
Why put Exa MCP behind an MCP gateway?
Connecting the Exa MCP server directly to each client means a separate credential per developer, no inventory of who can reach Exa through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Exa server, so sign-in runs through your identity provider, role-based access decides which teams can call which Exa tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Exa and to every other server in your catalog.
How do you connect Exa MCP through a gateway?
Add the Exa server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Exa tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Exa MCP?
Community-built Exa MCP servers wrap the same Exa surface but are not vendor-maintained. This catalog lists the official Exa MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.

AI everywhere.

Control here.

Talk to usLearn more