English Français العربية

io.github.CloudCorpRecords/researchsearch

Official registry Search and web

Web search, page extraction, crawling, and site mapping powered by the Tavily API.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @reneturcios/researchsearch
Claude Code 
claude mcp add researchsearch -- npx -y @reneturcios/researchsearch@0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "researchsearch": {
            "command": "npx",
            "args": [
                "-y",
                "@reneturcios/researchsearch@0.1.0",
                "mcp"
            ]
        }
    }
}
OCI package ghcr.io/cloudcorprecords/researchsearch:0.1.0
Claude Code 
claude mcp add researchsearch -- docker run -i --rm ghcr.io/cloudcorprecords/researchsearch:0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "researchsearch": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/cloudcorprecords/researchsearch:0.1.0",
                "mcp"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. researchsearch
  2. Install
  3. CLI
  4. MCP server
  5. Development
  6. License

researchsearch

researchsearch is a research desk for the web, powered by the Tavily API. It searches with ranked, content-bearing results (and an optional generated answer), pulls the clean text out of specific pages, crawls a site page by page under limits you set, and maps a site's structure so you can see what is there before you read it. It works from the command line or as an MCP server for agents.

A Tavily API key is required. Put it in the TAVILY_API_KEY environment variable; without it, every operation stops with an error that names the missing variable, before any request is made.

Install

export TAVILY_API_KEY="tvly-..."
npx @reneturcios/researchsearch search "composting basics"

Or run the container image:

docker run -i -e TAVILY_API_KEY="tvly-..." ghcr.io/cloudcorprecords/researchsearch

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

CLI

# Search; results print as JSON
researchsearch search "composting basics"
researchsearch search "rate decision" --topic news --days 3 --max-results 5 --answer

# Extract the clean content of one or more pages
researchsearch extract https://example.com/article
researchsearch extract https://example.com/a https://example.com/b --depth advanced

# Crawl a site from a starting page
researchsearch crawl https://example.com --max-depth 2 --limit 25
researchsearch crawl https://example.com --instructions "Focus on the guides"

# Map a site's structure (URLs only, no page content)
researchsearch map https://example.com --max-depth 1 --limit 50

researchsearch --version

Exit codes: 0 on success, 1 when an operation fails (a missing TAVILY_API_KEY, an HTTP error from the service, an unreachable host), 2 for usage errors.

MCP server

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

npx -y @reneturcios/researchsearch mcp

MCP client configuration:

{
  "mcpServers": {
    "researchsearch": {
      "command": "npx",
      "args": ["-y", "@reneturcios/researchsearch", "mcp"],
      "env": {
        "TAVILY_API_KEY": "tvly-..."
      }
    }
  }
}
Tools
ToolInputWhat it returns
tavily-searchquery (string, required), search_depth, topic, days, max_results, include_answer, include_raw_content, include_domains, exclude_domains (all optional)Ranked results with content excerpts and scores, plus a generated answer and raw page content when requested.
tavily-extracturls (string array, required), extract_depth, include_images, query (optional)The clean extracted content of each page, with failures reported separately.
tavily-crawlurl (string, required), max_depth, max_breadth, limit, instructions, extract_depth (optional)The pages visited from the starting URL, each with its extracted content.
tavily-mapurl (string, required), max_depth, max_breadth, limit, instructions (optional)The list of URLs reachable from the starting page, without page content.

Each tool is one call to the matching Tavily API endpoint. Only the parameters you set are sent — unset optionals are omitted so the service applies its own defaults — and each response is the service's JSON, passed back unchanged.

Development

npm install
npm 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.

Frequently asked questions

What is io.github.CloudCorpRecords/researchsearch?

Web search, page extraction, crawling, and site mapping powered by the Tavily API.

How do I install io.github.CloudCorpRecords/researchsearch?

It runs on your machine. In Claude Code: claude mcp add researchsearch -- npx -y @reneturcios/researchsearch@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.CloudCorpRecords/researchsearch need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.CloudCorpRecords/researchsearch open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.CloudCorpRecords/researchsearch?

It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.