scalpel
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@scalpelFind the definition and usages of the functionvalidateEmail."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
scalpel
Symbol-level codebase retrieval MCP server. Give an agent get_symbol(name) instead of a whole file — it returns just the definition and its usages.
Why
Reading whole files to answer one question about one symbol wastes context. scalpel avoids the read entirely instead of compressing it after the fact.
Related MCP server: codebase-rag
Setup
npm install && npm run build
# index a repo (lang: ts | python | go, default ts)
node dist/build-index.js /path/to/repo /path/to/repo/.scalpel/index.db [lang]
# run the MCP server over stdio
node dist/server.js /path/to/repo /path/to/repo/.scalpel/index.dbPoint an MCP client at it (stdio transport, args: <repoPath> <dbPath>).
Does it actually help?
Token cost: ~96% fewer tokens than reading whole files, across 4 repos and 3 languages, holds up under formal significance testing.
Real dollar cost: same story once billing/caching is accounted for, flat across weak/mid/strong model tiers.
Does it fix bugs faster? No net advantage. Tested on 57 real historical bugs — an agent with scalpel's tools and a plain grep/Read agent fix the same bugs, at basically the same speed. This is the paper's headline finding, not a footnote.
Full numbers, every caveat, every negative result: RESULTS.md.
This server cannot be deployed
Maintenance
Related MCP Connectors
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Ask a codebase what calls what: search, blast radius, paths between symbols, and diffs.
Project memory, semantic code search, and grounded agent context.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables LLMs to efficiently navigate large codebases by providing surgical access to specific code symbols via semantic search and call-graph queries.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.2MIT
- AlicenseNot gradedqualityAmaintenanceExposes a codebase's symbol graph and symbol-aware editing tools to AI agents, enabling targeted symbol lookup, impact analysis, and atomic multi-file edits with reduced context tokens.24 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables symbol-level codebase retrieval by returning a definition's source span and usage sites, avoiding whole-file reads to reduce token context.43 npmISC