Cortex
Index your local repository so Claude or Cursor can semantically search code and follow graph relationships instead of re-reading whole trees.
Overview
Cortex MCP is a MCP server for the Build phase that indexes your local repo for semantic search and graph relationships inside coding agents.
What is this MCP server?
- npm package @danielblomma/cortex-mcp at version 0.4.2 with stdio transport
- Semantic search over local repository content for faster agent navigation
- Graph relationships between symbols or files for impact and dependency questions
- Runs locally—keeps context on your machine for private repos
- GitHub-hosted open source with explicit repository URL in server.json
- Package version 0.4.2
- stdio transport via @danielblomma/cortex-mcp on npm
- Two headline capabilities: semantic search and graph relationships
Community signal: 12 GitHub stars.
What problem does it solve?
Large or unfamiliar codebases waste agent turns on blind file greps and missing cross-file dependencies.
Who is it for?
Solo developers who want a local, private repo brain for Claude Code or Cursor on active feature work.
Skip if: Builders who only need one-off answers and never run agents against the same repository repeatedly.
What do I get? / Deliverables
After install, your assistant queries indexed semantics and relationship graphs to land edits and reviews faster.
- Semantic search tools over your repository
- Graph relationship queries for dependencies and references
- Repeatable local context layer for coding sessions
Recommended MCP Servers
Journey fit
Repo context servers are adopted when you are actively building and need the agent to navigate a growing codebase. agent-tooling fits because Cortex is purpose-built to extend coding assistants with semantic search and relationship graphs, not to deploy infra.
How it compares
Local semantic repo graph MCP, not a hosted team wiki or generic web extractor.
Common Questions / FAQ
Who is Cortex MCP for?
Solo builders and small teams who run AI coding agents daily against a local git repo and need semantic navigation plus relationship context.
When should I use Cortex MCP?
Use it during build and review when the codebase is too large for naive search and you want persistent graph-aware context for the agent.
How do I add Cortex MCP to my agent?
Install @danielblomma/cortex-mcp from npm, add a stdio MCP server entry in Claude Code or Cursor pointing at the package binary, and point it at your project root.