TokenSaver
Shrink C#, Razor, and .NET context sent to coding agents using Roslyn-aware views so long sessions stay affordable.
Overview
TokenSaver is an MCP server for the Build phase that serves Roslyn-trimmed C#, Razor, and .NET file views to cut agent context tokens by roughly 50–95%.
What is this MCP server?
- Roslyn-based token-efficient views of C#, Razor, and .NET files
- Documented 50–95% token reduction range for assistant context
- NuGet package TokenSaver.Mcp v1.8.0 with stdio transport
- Optional TOKENSAVER_API_URL dashboard and TOKENSAVER_NO_TELEMETRY opt-out
- dnx runtime with --yes named argument for non-interactive agent hosts
- Package version 1.8.0
- Claimed 50–95% token reduction via Roslyn
- Default dashboard URL https://tokensavermcp.com
What problem does it solve?
.NET codebases blow agent context budgets when every request includes full Razor pages and large C# files.
Who is it for?
Indie developers shipping C# or Razor apps with Claude Code, Cursor, or Codex who routinely hit context limits.
Skip if: Pure JavaScript or Python shops with no .NET surface area.
What do I get? / Deliverables
Agents receive smaller, structure-preserving .NET views so you ship features in longer sessions with lower token spend.
- Token-reduced MCP views of C# and Razor sources
- Configurable telemetry opt-out via TOKENSAVER_NO_TELEMETRY
Recommended MCP Servers
Journey fit
Canonical shelf is Build because TokenSaver optimizes how agents read your codebase during implementation, not idea research or launch distribution. Agent-tooling is the right subphase: it is MCP infrastructure that changes token cost and fidelity when the agent works on .NET sources.
How it compares
.NET-focused context MCP server, not a general code formatter or linter.
Common Questions / FAQ
Who is TokenSaver for?
Solo builders and small teams on C#, Razor, or .NET stacks who use MCP agents and need cheaper, denser code context.
When should I use TokenSaver?
During Build when agents read large .NET solutions and token usage or truncation is slowing refactors and feature work.
How do I add TokenSaver to my agent?
Install the TokenSaver.Mcp NuGet package (v1.8.0), configure stdio MCP in your client, pass --yes if required, and set TOKENSAVER_API_URL or TOKENSAVER_NO_TELEMETRY as needed.