Show HN: Save Context from MCP Bloat
mcp-context-guard is a lightweight proxy tool designed to manage large responses from MCP servers by caching oversized tool outputs and returning minimal stubs. It introduces a seek_result tool that allows users to query cached content with filters like jq or grep to retrieve only relevant data. The tool supports both local and remote MCP servers, with transparent handling of OAuth flows and minimal impact on existing workflows.
- ▪mcp-context-guard prevents large tool responses from overwhelming the context window by caching them and returning small stubs.
- ▪The seek_result tool enables filtering cached responses using jq expressions or grep patterns to extract needed information.
- ▪It supports both local subprocess and remote HTTP MCP servers, with full OAuth transparency for remote setups.
- ▪Small responses under the size threshold pass through unchanged, preserving normal behavior.
- ▪The tool is distributed as a static binary with no runtime dependencies and requires Go 1.21+ for building from source.
2 outlets in our directory ran this story, first to last over 33 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/healqq/mcp-content-guard |
| Publication time | Sun, 17 May 2026 05:43:37 +0000 |
| Retrieval time | 2026-05-17T06:03:59.095Z |
| Last seen | 2026-05-17T06:03:59.095Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 8FbKjHZiUTiA · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
mcp-context-guard A lightweight wrapper for any MCP server that prevents large tool responses from flooding your context window. When a tool response exceeds a configurable size threshold, the proxy caches it and returns a small stub instead. You then query the cached response using the injected seek_result tool, applying a jq expression or grep pattern to extract only what you need. How it works MCP Client → mcp-context-guard → your MCP server (local subprocess or remote HTTP) The wrapper sits between your MCP client and any MCP server — local (stdio subprocess) or remote (Streamable HTTP). It: Passes through all tool schemas unchanged — the client sees the same tools as before, plus one new tool: seek_result.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.