Log inSubmit server
Argo logo

Argo

Searches 284 sources across 18 languages, combines web and local retrieval, and exposes 19 MCP tools for agent research.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Argo

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "argo": {
      "command": "npx",
      "args": [
        "-y",
        "argo-search"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

argo MCP server connects agents to 284 search sources spanning 99 domains, 18 languages, and areas such as academic, finance, code, news, shopping, and encyclopedic search. Its 19 MCP tools cover web search and fetching, local file retrieval, semantic search, logged-in searches, and JavaScript execution without a browser. Reach for argo when an agent needs source-aware research, multilingual results, local documents, or specialized search engines rather than a single web API. API keys are optional because free and local engines provide fallback routes.

Use cases

  • Search multilingual web sources for agent research
  • Find code, filenames, and document passages on a local machine
  • Retrieve evidence from specialized academic, financial, news, or shopping sources
  • Search login-gated content with an existing browser session
  • Run parallel research and retain an HTTP(S) source ledger

Key features

  • 284 search sources across 99 domains
  • 18-language and domain-aware routing
  • Web and local search in one MCP interface
  • BM25 plus vector semantic retrieval
  • 19 MCP tools with research workflows
  • Optional caching, reranking, deduplication, and source checks

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 14d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · argo-search (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars226Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.

How Argo works

What argo does

argo provides search and research capabilities for agents through MCP, with the same underlying implementation also available as a CLI, skill package, and DeepSeek Harness plugin. Its engine catalog contains 284 sources across 99 business areas and supports 18 languages, including Chinese, English, Japanese, and Korean.

Search can target broad web content or specialized sources for academic material, finance, code, news, entertainment, sports, macroeconomics, and other domains. Results can also include matches from the local machine. API keys may improve the quality or availability of particular sources, but the system can run without them by skipping unavailable authenticated engines and using free or local alternatives.

How it works

The MCP interface exposes 19 tools that map to the project's search and retrieval pipelines. The main path is ordinary search followed by page fetching when an agent needs evidence or additional context. A two-layer cache can reuse results for repeated queries, while ranking, numerical cross-checking, deduplication, and source safeguards help prepare material for agent consumption.

Four sub-skills organize specialized workflows:

  • local-search searches filenames, file contents, code symbols, and document structure using local engines. Local matches can be merged into an online search.
  • local-seek performs hybrid BM25 and vector retrieval over notes, memories, and document collections, progressing from file identification to context and paragraph-level reading.
  • ego-search uses a real browser and an existing login session to search content behind login requirements, including sites such as Zhihu, Xiaohongshu, and public-account platforms. It is disabled by default.
  • js-run executes suitable webpage JavaScript without opening a browser, targeting environment checks and pure computation tasks.

The argo_research workflow supports single-agent evidence gathering, while wide_research can coordinate parallel research tracks, maintain an HTTP(S) source ledger, and apply a quality gate to the resulting report.

Setup and configuration

Install the npm package globally with npm install -g argo-search, run it temporarily with npx -y argo-search, or use the GitHub package with npx -y github:taxueseek/argo. A source checkout is also supported through Git. The CLI can be tested with argo search "python asyncio error handling", and argo search --list-engines lists available engines.

For a persistent MCP connection, attach the server to an MCP client using the npm or local entry point. The project also provides an installation script and injection commands for several clients, including Claude Code, Cursor, Windsurf, Codex, and Cline. No API key is required for basic operation; engine-specific keys can be supplied when higher-quality or authenticated sources are needed.

Tools and capabilities

  • Web search across 284 sources with domain- and language-aware routing
  • Web page retrieval for follow-up evidence collection
  • Local file and document search with optional web-result merging
  • Hybrid semantic retrieval using BM25 and vectors
  • Logged-in professional search through a real browser
  • Browserless JavaScript execution for supported page scripts
  • Caching, TF-IDF reranking, numerical cross-checking, and MinHash deduplication
  • Parallel research with source ledgers and quality-gate results

Limitations and notes

Authenticated engines depend on their configured credentials and may be skipped when keys are unavailable. The logged-in search workflow is opt-in, and browserless JavaScript execution is intended for environment probing or pure computation rather than general browser automation.

The DeepSeek Harness integration offers native tools and a web-search/web-fetch seam in addition to MCP. When both the bundled provider and another provider are available, the web profile must explicitly select the argo search and fetch providers to avoid ambiguous routing. MCP tool definitions can add roughly 3.7K tokens per round for all 19 tools, so the plugin favors native tools for frequent searches and enables the full MCP surface when needed.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Argo

argo is an MCP server that connects AI agents to 284 web and local search sources across 18 languages and 99 domains. Its main tools provide search, page fetching, local file retrieval, semantic search, logged-in searches, browserless JavaScript execution, and research workflows for gathering and checking evidence.

Install it with npm, npx, the provided shell script, or a Git checkout. Use `npm install -g argo-search` for a global CLI, `npx -y argo-search` for a temporary run, or `npx -y github:taxueseek/argo` to run the GitHub version, then attach its MCP entry point to your client.

No, argo can run without API keys by using free and local engines and skipping sources that require credentials. Adding engine-specific keys can improve source quality or unlock authenticated providers.

Yes, argo includes local file and semantic search. It can look through filenames, document contents, code symbols, file structure, notes, memories, and other local collections, and local matches can be combined with network search results.

Yes, Cursor is one of the clients supported by argo's MCP setup and injection commands. The project also lists Claude Code, Windsurf, Codex, and Cline for automatic MCP configuration.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewArgo AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/argo?style=directory)](https://allmcps.com/mcp/argo)
HTML Embed
<a href="https://allmcps.com/mcp/argo"><img src="https://allmcps.com/api/badge/argo?style=directory" alt="Argo on AllMCPs" /></a>