MCP Gateway · Claude Cowork
Connect Exa to Claude Cowork
Cowork runs longer tasks, and research is a natural fit: search, read, compare and write it up. With Exa synced in as a plugin, a Cowork session can search the web and read full pages as steps in a bigger job. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties the session to a person.
- Category
- AI & search
- Tools
- 8
- Authentication
- None
- Claude Cowork
- Cowork tab in Claude Desktop
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.
Set up
Add Exa to Claude Cowork in 4 steps
- 01
Add Exa from the catalog
An admin finds Exa in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Exa
Give teams the
mcp:connectscope on the Exa server through team access or a role. Claude Cowork connects to the Exa server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Exa from Claude Cowork
The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, Exa's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Exa
Build a competitor landscape document
Give Cowork a list of competitors and it searches each one, reads their product pages, and assembles a comparison document you can edit.
Check a supplier list against websites
Hand Cowork a list of suppliers and have it read their sites in batches, noting what each company sells and where its pages say it operates.
Gather sources for a research report
Ask for the most useful articles on a topic. Cowork finds them, reads each one in full and writes a one-paragraph summary per source with its link.
Tools
8 tools
Each Exa tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.
web_search_exa
Search the web for any topic and get clean, ready-to-use content.
company_research_exa
[Deprecated: Use web_search_advanced_exa instead] Research any company to get business information, news, and insights.
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.
people_search_exa
[Deprecated: Use web_search_advanced_exa instead] Find people and their professional profiles.
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.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.
Tool logs
Gateway
Every Exa call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Exa tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Exa can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does a new Cowork session pick up changes to the Exa plugin?
Can Exa use in personal Claude accounts be governed?
How do Claude Cowork users get Exa?
Are Exa calls from Claude Cowork logged?
Connect more