Connect AI agents to Exa for web search, content fetching, and multi-step research.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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).
URLs to read. Batch multiple URLs in one call.
Maximum characters to extract per page (default: 3000)
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).
| Argument | Type | Description |
|---|---|---|
| urls* | array | URLs to read. Batch multiple URLs in one call. |
| maxCharacters | number | Maximum characters to extract per page (default: 3000) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"urls"
],
"properties": {
"urls": {
"type": "array",
"items": {
"type": "string"
},
"description": "URLs to read. Batch multiple URLs in one call."
},
"maxCharacters": {
"type": "number",
"minimum": 1,
"description": "Maximum characters to extract per page (default: 3000)"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| query* | string | Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:people John Doe software engineer'. |
| objective* | string | Goal for this search turn; say which documents should rank first, which should be excluded, and what specific facts or figures to pull from them. |
| numResults | number | Number of search results to return (default: 10). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query",
"objective"
],
"properties": {
"query": {
"type": "string",
"minLength": 1,
"description": "Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:people John Doe software engineer'."
},
"objective": {
"type": "string",
"maxLength": 4096,
"minLength": 1,
"description": "Goal for this search turn; say which documents should rank first, which should be excluded, and what specific facts or figures to pull from them."
},
"numResults": {
"type": "number",
"description": "Number of search results to return (default: 10)."
}
},
"additionalProperties": false
}