Deepsearch

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Oct 31, 2026

Neural web search, code context, and page crawling through the Exa API.

The publisher's own server: DeepSearch

VerifiedSTDIODesktop onlyWeb Search & Scraping Developer Tools

Server details

Identifier: io.github.CloudCorpRecords/deepsearch
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 31, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account CloudCorpRecords for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.CloudCorpRecords%2Fdeepsearch.svg)](https://sourceweft.com/mcp/io.github.CloudCorpRecords%2Fdeepsearch?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that gives an assistant Exa-powered neural web search, code context packs, and full-page crawling.

What you can do: Search the web with Exa and get matching pages with their text, titles and publication details
Gather code examples and documentation excerpts for a programming question, trimmed to a chosen token budget
Fetch the full text of one specific page by URL
All three tools accept token budgets clamped to 1000-50000, and empty results or failed fetches are reported as tool errors
When to use it: Useful when an assistant needs current web material, code samples and docs for a programming question, or the full text of a page you already know the URL of, without building your own search integration.
Requirements: Runs as a local stdio process via npx or the Docker image; needs an Exa API key in the EXA_API_KEY environment variable, sent to the API as the x-api-key header; network access to the Exa API; desktop only.

Before you install

Requires an Exa API key, which is stored in the client configuration and sent to Exa; queries and requested URLs go to a third-party API, so avoid sending confidential material; usage may be billed by Exa under your account.

Installation

In SourceWeft

Open Deepsearch in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

deepsearch

deepsearch asks Exa's neural index questions the way a researcher would. A plain search returns the pages that best match the meaning of a query, with their text already pulled in. A code question gets a context pack instead: examples and documentation excerpts gathered from across the web and sized to a token budget you choose. And when you already know the page you want, a crawl fetches that one page and hands back its words. It runs from the command line or as an MCP server for agents.

An Exa API key is required. Put it in the EXA_API_KEY environment variable; the key is sent to the API as the x-api-key header and never appears in output. When the variable is missing, every operation fails with an error that names it.

Install

Or run the container image:

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash

export EXA_API_KEY="your api key"
# Web search; --num-results defaults to 8deepsearch search "ferry electrification programs"deepsearch search "ferry electrification programs" --num-results 5
# Code context; --tokens sets the budget (1000-50000, default 5000)deepsearch code "React useState hook examples" --tokens 3000
# Fetch one page in fulldeepsearch crawl https://example.com/some/articledeepsearch crawl https://example.com/some/article --tokens 2000
# Machine-readable output for any commanddeepsearch search "ferry electrification programs" --json
deepsearch --version

export EXA_API_KEY="your api key"
# Web search; --num-results defaults to 8deepsearch search "ferry electrification programs"deepsearch search "ferry electrification programs" --num-results 5
# Code context; --tokens sets the budget (1000-50000, default 5000)deepsearch code "React useState hook examples" --tokens 3000
# Fetch one page in fulldeepsearch crawl https://example.com/some/articledeepsearch crawl https://example.com/some/article --tokens 2000
# Machine-readable output for any commanddeepsearch search "ferry electrification programs" --json
deepsearch --version

Exit codes: 0 on success, 1 when an operation fails (including a missing EXA_API_KEY or an API error), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

MCP client configuration:

json

{  "mcpServers": {    "deepsearch": {      "command": "npx",      "args": ["-y", "@reneturcios/deepsearch", "mcp"],      "env": { "EXA_API_KEY": "your api key" }    }  }}

{  "mcpServers": {    "deepsearch": {      "command": "npx",      "args": ["-y", "@reneturcios/deepsearch", "mcp"],      "env": { "EXA_API_KEY": "your api key" }    }  }}

Tools

These are the original server's default-enabled tools:

Tool	Input	What it returns
`web_search_exa`	`query` (string, required), `numResults` (number, optional, default 8)	Matching pages as a numbered text block: title, URL, publication details when known, and the page text the API supplied.
`get_code_context_exa`	`query` (string, required), `tokensNum` (number, optional, 1000–50000, default 5000)	Code examples and documentation excerpts for the question, each headed by its source, trimmed to the token budget.
`crawling_exa`	`url` (string, required), `tokensNum` (number, optional, default 5000)	The full text of that one page, titled, trimmed to the token budget.

Token budgets are clamped to the documented 1000–50000 range and are applied at roughly four characters per token. An empty result set is reported as such; a page the API cannot fetch, a missing key, or a failed API call is reported as a tool error.

Development

bash

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit eb25132

Tools

web_search_exa

Search the web with Exa and return relevant pages with their text content.

ParametersqueryrequirednumResults

get_code_context_exa

Find code examples and documentation for a programming question and return them as context.

ParametersqueryrequiredtokensNum

crawling_exa

Fetch the full text content of a specific web page by URL.

ParametersurlrequiredtokensNum

Version history

v0.1.0LatestOct 31, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Deepsearch integrations

DeepSearch

app.deepsearchOfficial publisher

DeepSearch is a remote MCP server that lets an assistant research people and companies from public sources, returning sourced dossiers, answers and lookups.

Streamable HTTPWeb executable

Web Search & Scraping12 toolsOct 25, 2026