English · 简体中文

SERA: Search Everything

One CLI and MCP toolkit to search the web, communities, databases, and archives.

Find the original sources. Read the material. Answer with evidence.

Quick start · Connect your agent · How it works · What you can search · Documentation

Need to verify a product specification, trace a claim to its source, or recover a page that disappeared? Ask your agent to investigate with SERA. It finds relevant sources, reads the original material, follows unresolved leads, and returns evidence you can revisit.

SERA connects your agent to tools for searching websites, code, communities, academic records, media databases, and internet archives. Your agent uses MCP; you can use the same workflows from a terminal. Search results lead to original pages, posts, comments, structured records, or historical snapshots, with URLs, versions, timestamps, and saved evidence IDs.

Quick start

Requires Node.js 22 or later. Run from source; an npm release is not yet available.

git clone https://github.com/GuraQwQ/sera-search.git
cd sera-search
npm ci --cache ./.cache/npm
npm run build
node dist/cli.js install --home ./.sera
node dist/cli.js capabilities --home ./.sera --sources bing,web --json

Search public sources and read the original pages:

node dist/cli.js research "TypeScript official release notes" --home ./.sera --sources bing --read-sources web --read-limit 3 --json

Public sources can be requested directly. Register credentials with login for sources that require an account. Use the same --home or SERA_HOME for every call; repeated install preserves existing configuration. Each response records actual network, login, and quota outcomes in runs.

The default install prepares SERA configuration without installing optional dependencies. Add repository tools, browser extraction, and HTML metadata parsing when needed:

node dist/cli.js install --home F:/tools/sera-data --components ghgrab,scrapling,metadata-parser --python D:/Python/python.exe --browser "D:/Apps/Edge/msedge.exe"

Use paths to your existing Python and Chromium-based browser. Components live under <home>/tools, with managed caches under <home>/cache/integrations. Repeating install verifies or repairs the selected components. See optional integrations for compatibility and backend tool discovery.

Already have a URL or object ID? Read it directly:

node dist/cli.js read-many "steam:105600" "sm8628149" --home ./.sera --keyword "release_date" --keyword "firstRetrieve" --json

See the CLI guide for commands and the configuration guide for API keys, proxies, and platform backends.

Related MCP server: Darus Search Engine

Connect your agent

Register a local stdio MCP server in your agent's configuration. Replace the paths with your installation and use the same data directory as the CLI:

{
  "mcpServers": {
    "sera": {
      "command": "node",
      "args": [
        "/absolute/path/to/sera-search/dist/cli.js",
        "mcp",
        "--home",
        "/absolute/path/to/sera-data"
      ]
    }
  }
}

On Windows, an absolute path such as F:/tools/sera-search/dist/cli.js also works.

Link the bundled Skill to your agent's standard skill directory for source selection and evidence workflows:

node dist/cli.js install --home /absolute/path/to/sera-data --skill-dir /absolute/path/to/agent-skills

The Skill links to the package directory, so keep that directory available. Start with the sources relevant to the task, then take the first batch of evidence; platform and credential details load when needed. Load the MCP configuration and Skill according to your client. See Agent Skill and MCP.

Then ask your agent:

Use SERA to trace Chinese-language support in the Steam edition of AIR.
Identify the exact product and version, then check the official store,
announcements, and historical snapshots. Report interface, subtitles,
and audio separately, with evidence, conflicts, and unresolved fields.

How it works

flowchart LR
    A[Your question] --> B[Agent identifies entities and missing facts]
    B --> C[SERA selects sources, searches, and reads]
    C --> D[Original material, versions, dates, evidence IDs]
    D --> E[Agent verifies and answers]
    E -->|Unresolved leads| B

• Choose the right material. Prefer official pages for versions, dates, and specifications; read original posts and comments for user feedback; locate original URLs and snapshots for historical questions. Account sources without valid credentials report that they are unavailable.

• Read less, keep the original. Use query and keywords to locate relevant passages. read-many deduplicates URLs and reads up to three documents concurrently. Fresh cached evidence can be reused; refresh requests a new copy.

• Follow the remaining gaps. Start a multi-part task with research and goals, review the returned passages, then send back the updated state for the remaining fields. For a multi-round CLI task, pass --state ./research-state.json from the first call; the CLI creates or updates that file, and you can edit verified fields before repeating the command. Previously examined URLs are skipped; fields become supported only after the agent verifies the evidence. See the workflow examples.

• Inspect the route taken. Default search selects sources by intent and switches backends after empty, unrelated, or failed results. Explicit sources aggregates the selected providers in parallel. Follow runs and any retryAfterSeconds before retrying a limited source; keep successful evidence while continuing other leads.

Full material remains available under its evidence ID. Passages retain Unicode offsets, and ranking organizes retrieval results. Multiple engines finding the same article still provide one original source. See the evidence guide for reading scope, content types, and follow-up retrieval.

What you can search

SERA currently registers 49 sources and exposes 13 MCP tools. Available operations depend on configuration, permissions, and the provider's actual response.

Game Wikis and visual-novel communities use catalogs loaded on demand:

node dist/cli.js search "Guide" --home ./.sera --sources wiki --platform terraria --group game-wikis --json
node dist/cli.js search "CLANNAD impressions" --home ./.sera --sources sites --platform fuwanovel --group galgame --json

MCP calls accept group:"game-wikis" or group:"galgame" within the same connection. See the source guide and domain routing guide for exact objects and reading scope.

Use backend ghgrab or backend scrapling to discover the upstream tools and their schemas; MCP clients use sera_backend. Scrapling sessions remain available within the same MCP connection. Google News aggregation records remain metadata until publisher text is actually retrieved; IPTV results describe catalog entries and stream URLs, with playback availability unverified. HTML metadata records page declarations, which require separate factual verification.

Results and evidence

Responses distinguish snippets, original text, metadata, subtitles, and comments. Partial failures preserve successful results; status, runs, and cacheWarnings identify follow-up work. Login, paid API access, rate limits, and snapshot availability are determined by actual requests.

Saved evidence can be located, paged, or refreshed from the chosen data directory. Multiple engines can lead to the same article; the agent verifies claims against original material, time and version boundaries, and publisher relationships.

Documentation

Detailed guides and the bundled Skill are currently written in Simplified Chinese.

Development and contributing

npm run check
npm run build
npm pack --ignore-scripts --dry-run --cache ./.cache/npm

The version comes from package.json; package-lock.json records reproducible installation inputs. Source code lives in src/, and catalogs live in catalogs/. CI checks types, builds the project, starts the CLI, and checks packaging on Windows, macOS, and Linux. New providers should declare their search, reading, authentication, and content scope.

Report a reproducible problem or suggest a source in an issue, or contribute an implementation or documentation improvement through a pull request.

Acknowledgments

SERA's shared entry points and evidence organization were inspired by REA. Provider integration, platform discovery, and query expansion also draw on MCP Omnisearch, OpenCLI, and search-skills.

License

MIT. Third-party services and source material retain their own terms and licenses; see third-party notices.