
TokenSave
io.github.aovestdipaperinoPublished by GitHub account aovestdipaperinov4.0.2Updated Nov 3, 2026
Code intelligence for 15+ languages: semantic graph queries instead of file reads. 37 MCP tools.
Overview
TokenSave builds a local semantic code graph of your project so an AI coding agent can query symbols, callers and context instead of grepping and reading files.
- What you can do
- Search code by meaning and retrieve symbols, relationships and snippets in one call
- Build task context with entry points, related symbols and source code
- Trace callers, callees and impact radius of a symbol; detect dead code and complexity
- Edit files through anchored replace, multi-replace and AST rewrite primitives, with automatic re-indexing
- Index per git branch and compare or search across branches
- Report code-health metrics, test mapping and token/cost savings
- When to use it
- Useful when an agent works in a large multi-language repository and burns tokens on repeated grep, glob and file reads, or when you want impact analysis and structured edits rather than raw file scanning.
- Requirements
- Runs as a local process on the user's machine (desktop only). Install via Cargo, Homebrew, Scoop or a prebuilt binary, then run the setup command to register the MCP server with your agent and initialize the project to create its local index. No API keys or environment variables are declared.
Installation
In SourceWeft
- Open TokenSave in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Semantic Code Intelligence for AI Coding Agents
Fewer tokens • Fewer tool calls • 100% local
[GitHub stars] [crates.io] [License: MIT] [Rust] [Built with AI — part of Enzo Lombardi's AI portfolio]
[macOS] [Linux] [Windows] [Hypercommit] [Listed in the Lulu MCP marketplace]
Why tokensave?
AI coding agents waste tokens exploring codebases. Every grep, glob, and file read costs money. On complex tasks, agents spawn multiple Explore sub-agents that scan hundreds of files just to build context.
tokensave gives agents a pre-indexed semantic knowledge graph. Instead of scanning files, the agent queries the graph and gets instant, structured answers -- the right symbols, their relationships, and source code, in one call.
How It Works
Without tokensave: Agents use grep, glob, and Read to scan files -- many API calls, high token usage.
With tokensave: Agents query the graph via MCP tools -- instant results, local processing, fewer tokens.
Key Features
Quick Start
1. Install
Choose one installation method:
You can also download a prebuilt binary and add it to your PATH.
To build unreleased code from the upstream master branch, see
Installing from upstream master.
Installation alternatives and language tiers
The default Cargo build includes all supported languages. For a smaller build:
Prebuilt release archives:
2. Configure your agent
Run the setup command to auto-detect your installed agents:
To choose an agent, use --agent (for example, codex, claude, or cursor):
Setup registers the MCP server and the agent's integration for Claude Code, Codex CLI, Gemini CLI, Cursor, Copilot, Kiro, Pi, Zed, and more than a dozen other agents. It also offers global Git hooks to keep initialized projects up to date. You can safely run setup again after upgrading. See Agent Integrations for project-local installs, several agents at once, and what setup writes for each agent.
3. Index your project
This creates a .tokensave/ directory with the knowledge graph database. A
repository you create with git init is initialized automatically on its first
commit or agent session (auto_init, on by default). After that,
tokensave sync updates the index incrementally, and a connected agent keeps it fresh automatically. Commands work
from any subdirectory of the project. See
Indexing and Freshness for details.
Documentation
The full documentation lives in docs/guide/ and is
mirrored to the GitHub Wiki.
The long-form User Guide walks through everyday use in more depth. To contribute, see CONTRIBUTING.md.
Origin
This project is a Rust port of the original CodeGraph TypeScript implementation by @colbymchenry. The port maintains the same architecture and MCP tool interface while leveraging Rust for performance and native tree-sitter bindings.
Building
To build from source, see Building from source and CONTRIBUTING.md.
Star History
[Star history]Sponsors
License
MIT License -- see LICENSE for details.
Source: README.md at commit 068aa3c
Tools
0Version history
1- v4.0.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts