Sense MCP Server

Codebase understanding for AI coding agents — symbol graph, blast radius, semantic search.

Local serverstdioPython

What is the Sense MCP Server?

Codebase understanding for AI coding agents — symbol graph, blast radius, semantic search.

The short version

Your AI agent reads 19 files to answer "who calls this function?" because it has the text of your codebase but never the map. It re-derives structure on every task, burns tokens chasing grep chains, and hallucinates dependencies that don't exist. Sense indexes your repo once and serves a symbol graph plus semantic code search over MCP. Claude Code, Cursor, Codex CLI, and any MCP client finish the same task in 10 tool calls instead of 19, on 156K tokens instead of 228K, with the same correctness (bench/).

What it needs from you

  • ~60 MB disk for the binary - 100-200 MB for the .sense/ index (varies with project size)

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
sense_graphSymbol relationships, callers, callees, inheritance, tests, dead code
sense_searchHybrid bi-encoder + cross-encoder semantic code search with keyword and text fallback
sense_blastBlast radius, affected code, affected tests, risk score
sense_conventionsDetected project conventions from source

Configuration

  • ~60 MB disk for the binary - 100-200 MB for the .sense/ index (varies with project size)

Example prompts to try

  • “Use Sense to sense graph.”
  • “Use Sense to sense search.”
  • “Use Sense to sense blast.”

Frequently asked questions

Codebase understanding for AI coding agents — symbol graph, blast radius, semantic search. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.