Hyperresearch is an MIT-licensed individual open-source project that persists research into a searchable markdown vault and ships a stdio MCP server so Claude Desktop, Cursor, and other clients can reuse that vault. Its strength is durability and portability: markdown is the source of truth and SQLite is only a rebuildable cache. Be aware that the project's self-reported benchmark results are pending third-party validation and that the README explicitly does not guarantee factual accuracy, leaving source judgment to the user.
Hyperresearch is an agent-driven research knowledge base. According to its README, it turns Claude Code into a deep research agent built around a tier-adaptive 16-step pipeline that produces an adversarially-audited report with full source provenance from a single prompt. Every source it reads lands in a persistent, searchable markdown-plus-SQLite vault, and each new session searches that vault before fetching anything new. The vault is reachable outside Claude Code through a built-in MCP server: install hyperresearch[mcp] and run hyperresearch mcp to speak stdio, exposing thirteen tools (search_notes, read_note, read_many, list_notes, get_backlinks, get_hubs, vault_status, lint_vault, check_source, list_sources, fetch_url, create_note, update_note) so Claude Desktop, Cursor, or any other MCP client can work the same vault. It is authored by jordan-gibbs as an individual open-source project under the MIT license, requires Python 3.11+ (3.11–3.13; 3.14 is not yet supported), and keeps notes as plain markdown with YAML frontmatter so the SQLite index is fully rebuildable and users are not locked into the tool.
1) Make sure Python 3.11–3.13 is available (3.14 is not yet supported). 2) Run pip install hyperresearch[mcp] to install the MCP-enabled build. 3) Run hyperresearch mcp, which starts the MCP server over stdio. 4) In Claude Desktop, Cursor, or another MCP-speaking client, configure hyperresearch mcp as the server command. The README does not provide a ready-to-copy client config snippet, so follow your client's MCP configuration format.
{
"mcpServers": {
"hyperresearch": {
"command": "hyperresearch",
"args": ["mcp"]
}
}
}