C
CoderDayton/semantic-cache-mcp
Semantic Cache MCP
★ 3·updated 2026-10-23
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 3 ★ · CoderDayton/semantic-cache-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
CoderDayton/semantic-cache-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
Semantic Cache MCP
Excerpted from the repository README (abridged)
Stop paying for the same file twice.
An MCP file cache for AI coding agents: a re-read costs ~40 tokens instead of the whole file.
Coding agents read the same files over and over: before an edit, after an edit, after every context compaction. A built-in Read sends the whole file each time. Semantic Cache MCP knows what your agent already holds. Measured on one 7,891-token file:
| Read | Built-in Read | Semantic Cache MCP |
| First read | 7,891 tokens | full file, plus a hash |
| Re-read, file unchanged | 7,891 tokens | 77 tokens |
| Re-read after a one-line edit | 7,891 tokens | 137 tokens (a diff) |
Across a 48-file project it saves 98.7% of re-read tokens, and an unchanged read takes 0.17 ms. It also gives your agent grep, BM25 search and glob over the cache, atomic edits with dry_run, and token-budgeted batch reads. Three runtime dependencies, no API keys, no GPU.
## Quick start
You need uv. In Claude Code:
bash
claude mcp add semantic-cache --scope user -- uvx semantic-cache-mcp
Any other client (Cursor, Claude Desktop, and others that take mcpServers JSON):
json
"mcpServers": {
"semantic-cache": {
"command": "uvx",
"args": ["semantic-cache-mcp"]
Configs for VS Code, Codex and OpenCode, and how to turn off the built-in file tools so the agent uses the cache: docs/clients.md.
## How it works
Every file the server sends comes with a content_hash. The agent passes it back as known_hash on the next read:
mermaid
flowchart LR
R["read(path, known_hash)"] --> M{"hash matches the file now?"}
M -- yes --> U["unchanged ~40 tokens"]
M -- "no, older version" --> D["diff of changed lines"]
M -- "no hash" --> F["full file + content_hash"]
No stale content. Every read checks the file on disk first. unchanged only answers when the hash matches the current bytes.
Forgetting is safe. After a compaction, the agent reads without the hash and gets the full file back.
Large files become maps. A file over max_size returns an outline of its definitions, not a blind cut.
Everything stays local. The cache is a SQLite file. One background daemon serves every client on your machine.
## Tools
read · batch_read · read_image · write · edit · batch_edit · edit_preview · delete · warm · grep · search · glob · stats · clear
Parameters and examples: docs/tools.md.
## FAQ
Is the search "semantic" in the embeddings sense? No. search is BM25 keyword ranking and grep is exact. No model to download, no GPU, no API key.
Does it send my code anywhere? No. The only network request is a one-time download of the o200k tokenizer file, checked against a SHA-256 hash.
An MCP file cache for AI coding agents: a re-read costs ~40 tokens instead of the whole file.
Coding agents read the same files over and over: before an edit, after an edit, after every context compaction. A built-in Read sends the whole file each time. Semantic Cache MCP knows what your agent already holds. Measured on one 7,891-token file:
| Read | Built-in Read | Semantic Cache MCP |
| First read | 7,891 tokens | full file, plus a hash |
| Re-read, file unchanged | 7,891 tokens | 77 tokens |
| Re-read after a one-line edit | 7,891 tokens | 137 tokens (a diff) |
Across a 48-file project it saves 98.7% of re-read tokens, and an unchanged read takes 0.17 ms. It also gives your agent grep, BM25 search and glob over the cache, atomic edits with dry_run, and token-budgeted batch reads. Three runtime dependencies, no API keys, no GPU.
## Quick start
You need uv. In Claude Code:
bash
claude mcp add semantic-cache --scope user -- uvx semantic-cache-mcp
Any other client (Cursor, Claude Desktop, and others that take mcpServers JSON):
json
"mcpServers": {
"semantic-cache": {
"command": "uvx",
"args": ["semantic-cache-mcp"]
Configs for VS Code, Codex and OpenCode, and how to turn off the built-in file tools so the agent uses the cache: docs/clients.md.
## How it works
Every file the server sends comes with a content_hash. The agent passes it back as known_hash on the next read:
mermaid
flowchart LR
R["read(path, known_hash)"] --> M{"hash matches the file now?"}
M -- yes --> U["unchanged ~40 tokens"]
M -- "no, older version" --> D["diff of changed lines"]
M -- "no hash" --> F["full file + content_hash"]
No stale content. Every read checks the file on disk first. unchanged only answers when the hash matches the current bytes.
Forgetting is safe. After a compaction, the agent reads without the hash and gets the full file back.
Large files become maps. A file over max_size returns an outline of its definitions, not a blind cut.
Everything stays local. The cache is a SQLite file. One background daemon serves every client on your machine.
## Tools
read · batch_read · read_image · write · edit · batch_edit · edit_preview · delete · warm · grep · search · glob · stats · clear
Parameters and examples: docs/tools.md.
## FAQ
Is the search "semantic" in the embeddings sense? No. search is BM25 keyword ranking and grep is exact. No model to download, no GPU, no API key.
Does it send my code anywhere? No. The only network request is a one-time download of the o200k tokenizer file, checked against a SHA-256 hash.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/coderdayton-semantic-cache-mcp/)
- Source
- awesome · https://github.com/CoderDayton/semantic-cache-mcp
- Browse by field
- MCP servers
- Traction
- 3 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.