Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read large logs, JSON and docs in a fraction of the tokens. Offline, fact-preserving optimizer.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"latent-gate": {
"command": "uvx",
"args": [
"latent-gate",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add latent-gate -- uvx latent-gate mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"latent-gate": {
"command": "uvx",
"args": [
"latent-gate",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"latent-gate": {
"type": "stdio",
"command": "uvx",
"args": [
"latent-gate",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account KathanModh259, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.4.2) reached the registry 30 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server that shrinks logs, JSON, docs and web pages before your AI reads them — offline, deterministic, in ~3ms, no API key. 66% fewer tokens across a mixed dev corpus; 90%+ on repetitive logs.
Use in Claude | Quick Start | Python API | REST API | Monitoring | Load Testing | Deployment | AI Tools | Benchmarks | Contributing
[Try it in your browser →](https://kathanmodh259.github.io/latent-gate/) The real optimizer runs on your machine via WebAssembly; nothing you paste is uploaded.
A 400-line error log, read through LatentGate (balanced, measured with tiktoken):
BEFORE 13,641 tokens
2026-10-08 09:00:00 ERROR order 10000 failed: payment gateway timeout after 2982ms (retry 1/3) ... 398 more lines in the same shape ...
AFTER 145 tokens (98.9% saved) 2026-10-08 09:00:00 INFO app started, 3 workers 2026-10-08 09:00:00 ERROR order 10000 failed: payment gateway timeout after 2982ms (retry 1/3) [… 398 similar lines: order 10001…10398, 2900…3100 ms …] 2026-10-08 09:06:39 ERROR order 10399 failed: payment gateway timeout after 3030ms (retry 1/3) 2026-10-08 09:07:00 FATAL circuit breaker open for payments-api
Install it into Claude Code in one line, then ask *"read app.log and tell me why orders fail"*:
claude mcp add --scope user latent-gate -- uvx --from "latent-gate[mcp,tokens]" latent-gate-mcp
What you can rely on: the same input always gives the same output (so provider prompt caching keeps working); output is never larger than input; code blocks, URLs and quoted strings come back byte-for-byte; level="lossless" changes nothing but whitespace, JSON formatting and exact duplicates. What you trade at the default level: runs of near-identical lines are folded to first, last and value ranges, so individual IDs inside a folded run are not kept. The full corpus, including where it loses facts, is in Cost Benchmarks and reproducible with latent-gate --optimizer-benchmark.
Works in Claude Code, Claude Desktop, Cursor, Cline, Continue and Zed, free and offline.
Don't want to install anything? The official hosted LatentGate on mcprush also runs where local servers can't, such as claude.ai on the web and mobile. It has a free tier (300 calls a month) and paid plans from $9/month.
Every time you send an image or long prompt to GPT-4o / Claude / Gemini, you burn 1,000+ tokens on processing that could happen locally for free.
Traditional: Image -> Cloud LLM (1,200 tokens) -> Answer
LatentGate: Image -> Local Ollama (FREE) -> Cloud LLM (200 tokens) -> Answer
| Feature | Description |
|---|---|
| Local-First | Vision and text compression runs on Ollama (free, no API key needed) |
| Token Optimizer | Deterministic, fact-preserving compression: 66% fewer tokens on a realistic dev corpus in ~1ms (benchmark) |
| MCP Server | Works with Claude Desktop, Cursor, Cline, Continue, Zed |
| Selective Decoding | For video, only call API when scene changes (~2.85x fewer calls) with cosine similarity |
| Text Compression | Long prompts, conversations, RAG docs compressed locally |
| Speed Optimized | Connection pooling, model preloading, parallel processing |
| Multi-Provider | OpenAI, Anthropic, Google, Groq, DeepSeek, Together, Azure, AWS Bedrock, Ollama, or any OpenAI-compatible endpoint |
| REST API | FastAPI server for web application integration |
| Video Processing | Direct video file input with automatic frame extraction |
| Cost Tracking | Persistent cost tracking with SQLite analytics and exportable reports |
| Async Support | Non-blocking async methods for FastAPI, aiohttp, etc. |
| Streaming Responses | Stream responses from remote LLMs |
| Config Persistence | YAML/TOML config files with environment variable overrides |
| Structured Logging | JSON-formatted logging with rotation and correlation IDs |
| Docker Support | Dockerfile and docker-compose for easy deployment |
| Plugin System | Custom processors for domain-specific compression |
| Multi-Language | Support for 30+ languages with automatic detection |
LatentGate plugs into Claude as an MCP server. Its optimizer tools work offline, with no Ollama and no API key — Claude reads big logs, JSON dumps and docs through it and spends a fraction of the context. A 400-line error log goes from 14,400 to ~100 tokens.
Requires uv (uvx fetches LatentGate from PyPI on first run). The first run downloads dependencies, which can exceed Claude's 30-second MCP startup limit on a slow connection; run this once beforehand (later starts take ~2s):
uvx --from "latent-gate[mcp,tokens]" latent-gate --optimizer-benchmark
Claude Code — plugin (MCP server + a skill that tells Claude when to use it):
/plugin marketplace add KathanModh259/latent-gate
/plugin install latent-gate@latent-gate
Claude Code — MCP server only:
claude mcp add latent-gate -- uvx --from "latent-gate[mcp,tokens]" latent-gate-mcp
Any agent — from the Agensi marketplace: LatentGate Context Saver is the official skill for Claude Code, Cursor, Codex CLI and 20+ other agents. It sets LatentGate up if it's missing, works with the local and hosted editions, and tells your agent when to use it.
Claude Desktop — add to claude_desktop_config.json and restart:
{
"mcpServers": { "latent-gate": { "command": "uvx", "args": ["--from", "latent-gate[mcp,tokens]", "latent-gate-mcp"] } } }
Then just ask: *"Read logs/app.log with latent-gate and tell me why orders fail."*
| Tool | Needs Ollama | What it does |
|---|---|---|
read_file_optimized | no | Read a text file and return its optimized form (use for files you read, not files you edit) |
optimize_text | no | Optimize text you already have, optionally toward a question / max_tokens budget |
count_tokens | no | Count tokens (tiktoken o200k_base) |
compress_image | yes | Describe an image locally as a ~150-token scene payload |
compress_text / compress_conversation / compress_documents | yes | Optimizer + fact-checked local-LLM compression |
get_stats | yes | Session statistics |
# Core install
pip install latent-gate
pip install latent-gate[mcp]
pip install latent-gate[api]
pip install latent-gate[video]
pip install latent-gate[embeddings]
pip install latent-gate[langchain]
pip install latent-gate[bedrock]
pip install latent-gate[tokens]
pip install latent-gate[all]
ollama pull llava:7b # Vision model (required for image queries)
ollama pull llama3:8b # Text model (required for text compression & prediction)
chmod +x scripts/quickstart.sh
./scripts/quickstart.sh
This starts everything: Ollama → pulls models → API server → website. See scripts/quickstart.sh for options like --no-pull, --no-website, --port 9000.
# Image query
latent-gate photo.jpg "What is in this image?" --provider ollama -v
latent-gate --text "Your long prompt here..." --provider ollama -v
latent-gate --text-file prompt.txt --provider openai -v
latent-gate photo.jpg "Analyze" --text "Extra context..." -v
latent-gate photo.jpg "Describe" --json -v
cat prompt.txt | latent-gate --text-file - --compress-only --deterministic --level balanced
latent-gate --optimizer-benchmark
latent-gate --benchmark --benchmark-output reports/benchmark.json
latent-gate-api
For API deployments, restrict direct image-path reads to trusted directories:
set LATENTGATE_ALLOWED_IMAGE_ROOTS=C:\safe-images;D:\datasets
latent-gate-api
Benchmark before releases so speed and savings are measured, not guessed:
latent-gate --benchmark --json
from latent_gate import LatentGatePipeline, PipelineConfig
config = PipelineConfig( vision_model="llava:7b", predictor_model="llama3:8b", remote_provider="openai", remote_model="gpt-4o-mini", )
with LatentGatePipeline(config) as pipeline: result = pipeline.query("photo.jpg", "What is in this image?")
print(result["answer"]) print(f"Tokens sent: ~{result['tokens_estimated']}") print(f"Timing: {result['timing']}")
# Long prompt compression
result = pipeline.query_text("Your 500-word prompt here...", mode="auto")
messages = [ {"role": "user", "content": "Help me with Kubernetes setup"}, {"role": "assistant", "content": "Sure! What's your target configuration?"}, {"role": "user", "content": "3 nodes, t3.large, us-east-1 with autoscaling"}, ] result = pipeline.query_conversation(messages, "Now give me the setup commands")
documents = ["doc1 text...", "doc2 text...", "doc3 text..."] result = pipeline.query_documents(documents, "How do I implement JWT refresh?")
result = pipeline.query_universal(text="Explain this code...", image="screenshot.png")
# Sequential with selective decoding (skips redundant API calls)
results = pipeline.query_batch(image_paths, "Describe each scene
Only the beginning is shown; read the rest in the repo