Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-context-dedup deduplicate this repetitive output"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-context-dedup
Zero-dependency semantic context stream compression & token deduplication engine for MCP tools (achieving 60%–80% LLM token savings).
💰 60%–80% Token Savings: Saves LLM prompt token costs on verbose stdout streams and repetitive log outputs.
⚡ Zero External Dependencies: Built 100% on Python Standard Library.
🧹 Traceback & Log Deduplication: Collapses repeated traceback frames and identical log lines into [Repeated Nx] count blocks.
🗜️ JSON Array Summarization: Truncates large homogeneous JSON arrays while preserving top/bottom schema context.
🛠️ Stdio MCP Server: Ready for instant integration into Claude Desktop, Cursor, and Windsurf via uvx.
Related MCP server: logslim-mcp
+-------------------+ +--------------------------+ +------------------------+
| Verbose MCP Output| --> | mcpcontextdedup Engine | --> | Compressed Stream |
| (14k Tokens) | | (Deduplication & JSON) | | (2.8k Tokens / 80% Off)|
+-------------------+ +--------------------------+ +------------------------+uvx mcp-context-dedupfrom mcpcontextdedup import compress_context
raw_log = "error: connection reset\nerror: connection reset\nerror: connection reset\n"
res = compress_context(raw_log)
print(f"Reduction: {res.reduction_percentage}%")
print(res.text)
# Output:
# Reduction: 66.7%
# error: connection reset [Repeated 3x]Add to your claude_desktop_config.json:
{
"mcpServers": {
"context-dedup": {
"command": "uvx",
"args": ["mcp-context-dedup"]
}
}
}Output Type | Original Tokens | Compressed Tokens | Token Savings | Execution Time |
Repeated Log Stream (1,000 lines) | 14,200 tokens | 280 tokens | 98.0% Savings | 1.8 ms |
Large JSON API Array (500 items) | 28,500 tokens | 4,200 tokens | 85.3% Savings | 3.4 ms |
Python Traceback Burst (50 frames) | 8,400 tokens | 1,600 tokens | 81.0% Savings | 1.1 ms |
100% Local & Offline: Operates strictly over local stdio with zero network calls.
Zero Telemetry: No analytics, no tracking, and no phone-home mechanisms.
MIT © Abhishek Prasad
Compress verbose tool outputs and deduplicate log lines to save LLM prompt tokens.
| Name | Required | Description | Default |
|---|---|---|---|
| raw_text | Yes | Raw verbose stdout/stderr string |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the actions (compress, deduplicate) but does not disclose the output format, whether the compression is lossy, or how it handles edge cases like empty input. Without an output schema or annotations, critical behavioral context is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that is front-loaded with the primary action and includes the motivating purpose. Every word contributes value; no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity (1 parameter, no output schema, no annotations), the description conveys the core functionality but lacks details about the return value and potential lossiness. It is minimally viable but has clear gaps for a tool that transforms user input.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter 'raw_text', which is adequately described as 'Raw verbose stdout/stderr string'. The description adds little beyond the schema, but since the schema already covers semantics, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Compress') and resource ('verbose tool outputs'), and adds a second distinct action ('deduplicate log lines') with a clear goal ('to save LLM prompt tokens'). This leaves no ambiguity about what the tool does, even without sibling context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use the tool: when dealing with verbose tool outputs that need token savings. It does not mention explicit exclusions or alternatives, but with no siblings present, the context is sufficient for a 4.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0compress_mcp_outputScored across 1 tool
With only one tool, there is no possibility of confusion or overlapping purposes. The tool's unique function is clear.
The single tool follows a clear verb_noun pattern (compress_mcp_output), and with only one tool, there are no inconsistencies to evaluate.
The server has a single tool, which feels borderline for a typical server. However, the narrow purpose of context deduplication makes one tool arguably sufficient, but it is still on the thin side.
The tool fully addresses the server's stated purpose of compressing MCP outputs and deduplicating logs. There are no obvious missing operations for this narrowly defined domain.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
A paid remote MCP for OpenAI Codex context compressor, built to return verdicts, receipts, usage log
Multiple MCP tools, persistent graph memory, token-saving data pointers, and more.
Same functionality, consuming only 1/20 of the context window tokens.
Zero-auth MCP: image optimize, cited storage/format data, and dev utilities LLMs get wrong.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/prasadabhishek/mcp-context-dedup'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
