vicem
Related Servers
Alternatives to vicem
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides reversible context compression for AI agents, reducing token usage while preserving the ability to retrieve original content, and serves as an MCP server for integration with tools like GitHub Copilot and Claude Code.31Apache 2.0
- AlicenseAqualityBmaintenanceDeterministic, local-first context optimization for AI coding agents. Automatically compresses raw development session data (messages, tool logs, error stack traces, and git diffs) into a compact, task-specific context window. Operates 100% locally with zero external LLM dependencies, ensuring your source code never leaves your machine.6103 npmMIT
- AlicenseAqualityBmaintenanceLocal-first MCP server that watches your coding sessions and injects a compact summary at the start of each new session. 85.6% token reduction, SQLite storage, no cloud. Works with Claude Code, Cursor, Cline, and Windsurf.15241 npm9MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP-compliant clients to dynamically shrink long-horizon context windows, pruning verbose tool outputs, HTML boilerplate, and semantic redundancy by roughly 40-70% without frontier LLM round-trips. Runs deterministically as a zero-dependency Python stdio server, accepting a payload plus optional compression and risk-bound options.7-
- AlicenseNot gradedqualityDmaintenanceA task-aware context compression layer for Agent workflows, RAG pipelines, and AI Coding assistants, reducing noisy logs, retrieval chunks, and code context into high-signal LLM inputs via CLI, Python SDK, and MCP.20 PyPI322MIT
- AlicenseNot gradedqualityBmaintenanceCompresses multi-turn conversation history by stripping verbose boilerplate and filler tokens while preserving critical tool parameters and named entities, deterministically cutting inference costs by 40-60%. Runs as a zero-dependency Python MCP server or importable module, compatible with Claude Desktop, Cursor, and other MCP runtimes.7MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: create a baton, read a baton, restore a skeletonized symbol, or validate safety guards. The descriptions explicitly cross-reference alternatives and state when not to use each tool, leaving no practical ambiguity.
All tool names use the same `vicem_` prefix followed by a snake_case verb_noun pattern: `create_baton`, `read_baton`, `rehydrate`, and `check_guard`. There are no deviations in casing or verb style.
Four tools tightly map to the handoff workflow: create, read, rehydrate, and guard. The set is small but each tool has a necessary, non-overlapping purpose for this focused protocol.
The core lifecycle is covered: creating and reading a baton, restoring skeletonized symbols, and validating edits before commit. Minor gaps exist around explicit snapshot restore/cleanup or standalone ledger inspection, though idempotent create and read_baton's Section 6 index largely mitigate them.