# HydraScope MCP

> HydraScope MCP is an open-source MCP server for agent tooling. MCP server giving coding agents graph-based context: skills, tools, ADR lineage on HydraDB. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, Self-hosted, Web
- **Repository:** https://github.com/kruschdev/hydrascope
- **MCP Registry name:** dev.krusch/hydrascope
- **Categories:** [agent tooling](https://ai-powered.com/categories/agent-tooling)
- **Listing updated:** 2026-11-19

## About

The README says HydraScope is a context layer that stores an agent's skills, MCP tool definitions, resolved entities and code/ADR history in a self-hosted HydraDB graph, then traverses only the subgraph a given task needs. Instead of loading every tool schema into the prompt, the server returns a compact slice of relevant tools, mandatory follow-up checks and current (non-superseded) rules.

Writes flow back into the graph after each run, so newly resolved entity aliases and frequently co-used tool chains are stored for later turns. Temporal SUPERSEDES edges let retired tools and ADRs be blocked at HEAD while historical lookups remain possible.

The project is aimed at developers and SRE or engineering teams running several MCP servers with coding, incident-response or operations agents. It is distributed as an npm package and works over stdio with clients such as Claude Code, Cursor and Windsurf, and it also includes a local web UI and CLI benchmarks.

## Features

- **Compact tool context:** Returns only the tools and rules a task requires rather than preloading every MCP schema into the prompt.
- **Temporal supersession tracking:** Uses SUPERSEDES edges to block retired tools and ADRs while keeping historical as-of queries available.
- **Persistent entity resolution:** Stores resolved entity aliases in the graph so later runs skip repeated lookup round-trips.
- **Code and ADR lineage:** Traverses multi-hop relationships between skills, tools, code symbols and architecture decision records.
- **Stdio MCP server:** Runs as an npm package over stdio and can be attached to common AI coding clients via JSON config.
- **Built-in benchmarks:** Includes CLI commands and a UI for reproducing context-retrieval and load benchmarks against vector search.

## Good for

- Reducing prompt-window token use when an agent connects to many MCP servers
- Preventing coding agents from calling deprecated tools or following retired ADRs
- Keeping multi-turn operational agents from repeating entity lookups across runs
- Benchmarking graph-based context retrieval against dense vector search on a local repository

## Install

### Claude Code (Terminal)

```sh
claude mcp add hydrascope -- npx -y hydrascope
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "hydrascope": {
      "command": "npx",
      "args": [
        "-y",
        "hydrascope"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "hydrascope": {
      "command": "npx",
      "args": [
        "-y",
        "hydrascope"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "hydrascope": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "hydrascope"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "hydrascope": {
      "command": "npx",
      "args": [
        "-y",
        "hydrascope"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "hydrascope": {
      "command": "npx",
      "args": [
        "-y",
        "hydrascope"
      ]
    }
  }
}
```

## FAQ

### How is HydraScope installed?

The registry lists it as the npm package hydrascope version 0.1.1 using stdio transport. The README also describes cloning the repository, running npm install and npm run build, and starting the server.

### Does HydraScope MCP require a separate database?

Yes. The README says it is built on self-hosted HydraDB v0.4.0, which can be started with Docker Compose using a provided profile.

### What license does HydraScope MCP use?

The README states the HydraScope project is released under the MIT License. It notes that HydraDB itself is under ELv2.

### Is HydraScope MCP free?

Yes. HydraScope MCP is open source, so you can use and self-host it for free.

### How do I add HydraScope MCP to Claude Code?

Run this command in your terminal: claude mcp add hydrascope -- npx -y hydrascope

### What are the best alternatives to HydraScope MCP?

The closest alternatives to HydraScope MCP are Switchhboard MCP, Context First MCP, The Context Company, toolhive and World Model MCP.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [Switchhboard MCP](https://ai-powered.com/mcp/switchhboard-mcp): Switchhboard MCP is an open-source MCP server for agent tooling.
- [Context First MCP](https://ai-powered.com/mcp/context-first-mcp): Context First MCP is an open-source MCP server for agent tooling.
- [The Context Company](https://ai-powered.com/mcp/the-context-company): The Context Company is an MCP server for agent tooling.
- [toolhive](https://ai-powered.com/mcp/toolhive): toolhive is an open-source MCP server for agent tooling.
- [World Model MCP](https://ai-powered.com/mcp/world-model-mcp-2): World Model MCP is an open-source MCP server for agent tooling.
- [nhi1.org](https://ai-powered.com/mcp/nhi1-org): nhi1.org is an open-source MCP server for agent tooling.
- [Superagenticmcp](https://ai-powered.com/mcp/superagenticmcp): Superagenticmcp is an open-source MCP server for agent tooling.
- [MCP Audit](https://ai-powered.com/mcp/mcp-audit-3): MCP Audit is an open-source MCP server for agent tooling.

---
Source: https://ai-powered.com/mcp/hydrascope-mcp
