Token-efficient .NET codebase context for AI coding agents: skeleton, scoping, change-aware fusion.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"fuse": {
"args": [
"mcp",
"serve"
],
"type": "stdio",
"command": "fuse"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Fuse is a Model Context Protocol server for AI-assisted development on .NET. It hands your coding agent (Claude Code, Cursor, GitHub Copilot) the right code, scoped and reduced, in a single call, instead of letting it burn its context window opening thousands of files during the explore phase. It cuts input tokens while keeping the public API intact, scopes to the files a task needs, and trims the round-trips an agent makes. The same engine is also a fuse CLI.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Litenova-Solutions/fuse and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Fuse is a local .NET tool with a persistent semantic index, typed-graph wiring
resolution, reduced task-scoped source, and pre-write compiler verification for
coding agents. It indexes a solution through MSBuild and Roslyn, stores the result
in .fuse/fuse.db, and reuses it across agent turns instead of rediscovering the
same structure through repeated file reads and text searches.
From a .NET project inside a Git repository:
dotnet tool install -g Fuse
fuse mcp install --rules
The installer supports Claude Code, Cursor, GitHub Copilot, OpenCode, Kilo Code, Codex,
and Grok Build. Use --client <name> to configure one client; the default all configures
all seven for the selected scope. fuse mcp install writes MCP client registration only.
--rules also writes the client's documented instruction file, such as AGENTS.md or
CLAUDE.md; it does not install a skill. --with-hooks separately writes project-scoped
Claude Code hooks. See Connect your coding agent
for the exact file and scope matrix.
Reload your MCP client, then ask:
Resolve IOrderService to its implementation, then check the proposed OrderService.cs edit
with fuse_check before writing it.
When the MCP server starts, its shared local daemon begins warming .fuse/fuse.db in
the background. A cold read waits for a bounded syntax-first pass and reports when the
semantic graph is still upgrading. Run fuse index when you want a synchronous full
index before connecting the agent. fuse mcp install --rules also adds .fuse/ to
.gitignore at project scope.
Every MCP operation except fuse_reduce requires a Git repository identity. Fuse walks upward to the nearest
.git directory or file, so a call from a nested source or output folder uses the same
repository-root daemon, lock, and index. A non-Git folder returns
workspace_identity_unresolved: without starting a daemon or writing an index;
fuse_reduce remains available. Each warm index records its repository root and complete
file inventory. A missing or incomplete manifest rebuilds automatically even when the
database already contains file rows.
Analysis runs locally and can work offline. Fuse walks a typed graph of DI registrations, handlers, routes, and callers, emits reduced source for a selected scope, and lets a coding agent typecheck proposed single-file content before writing it. No model is required. The optional update check can contact NuGet, and build-grade operations can use the package feeds configured for the repository.
Coding agents can inspect a repository through file reads, grep, and regex. On a large solution, those operations can rediscover the same symbols, references, registrations, and project structure across several turns. Fuse performs that discovery through MSBuild and Roslyn, persists the result, and incrementally re-indexes files as they change.
When a project loa