Specific implementation researched
Exa
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Exa
- Publisher
- Exa
- Origin
- Officially from the named publisher
- Deployment mode
- Remote and local
- Transport
- HTTP remote; lokales npm-Paket für stdio-Clients dokumentiert.
- Authentication
- Limited search and fetch without a key; OAuth or an API key for account access and Exa Agent.
- Read capabilities
- Web search · Retrieve page content · Retrieve code context and research
- Write capabilities
- No confirmed information
- Permissions
- Anonymous use is limited; agent features require login or an API key.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Setup documented | Documentation ↗ |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
Exa MCP - Exa ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.exa.ai/mcp