ctxfeed
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., "@ctxfeedwhere is the auth middleware defined?"
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.
一句钩子:ChatGPT 把项目卡在 40 个文件、Claude 的 200k 窗口按 token 计费烧到撞限额——ctxfeed 把整个 1000+ 文件仓库塞进 GLM-5.2 的 1M 上下文喂给 coding agent,一次 MCP 往返拿到答案。
核心原语是 ShardPlan——缓存感知的文件摄入顺序,让 ctxfeed 不只是"调 GLM 带文件"。stable_prefix(依赖清单、README、类型定义先入)+ delta(只重摄入改动文件)是可拥有的部分:一个确定性的、prefix-cache 对齐的摄入计划,原始 GLM/DeepSeek API 不提供。没有它,判词说产品会退化成"成本套利 RAG 包装"。
为什么是现在
GLM-5.2 的 1M MIT 许可上下文窗口是 2026 年的已发布实物(r/LocalLLaMA 引述"Kimi K3 in the next few hours. DeepSeek V4 GA later in the week"——多家 CN 长上下文模型同周落地),MCP 给了 coding agent 一个标准摄入缝。ctxfeed 把这波供给侧长上下文变成 Agent 能直接消费的项目上下文后端——langgenius/dify 这类国产 origin 的 agent 平台生态正是它的落地点:dify 用户撞到上下文上限时,ctxfeed 是那个喂全仓库的 MCP 后端。
uvx ctxfeed init # 扫描仓库、构建 ShardPlan、摄入(默认 dry-run,无需 key)
uvx ctxfeed cost # 单次查询 token 成本对比 Opus进 live 模式(真实 GLM-5.2 调用):
export ZHIPU_API_KEY=glm-...
uvx ctxfeed init # 真 GLM-5.2 摄入╭──────────────────────────────────────────────────────────╮
│ ctxfeed init — /path/to/repo │
│ model=GLM-5.2 (1M ctx) mode=dry-run │
╰──────────────────────────────────────────────────────────╯
┌─────────────────────┬────────────────────────────┐
│ files accepted │ 1024 (vs ChatGPT's 40) │
│ stable_prefix │ 12 (3_421t) │
│ repo_body │ 1012 (118_733t) │
│ tokens │ 122,154 / 1,000,000 (12.2%)│
│ cache hit │ 0% │
│ delta (new/changed) │ 1024 │
└─────────────────────┴────────────────────────────┘
╭──────────────────────────────────────────────────────────╮
│ 1024 files accepted (25.6x ChatGPT's cap, PAST) │
╰──────────────────────────────────────────────────────────╯# 查看某文件/目录加进 plan 后的 layer + token 数(只读,不改缓存)
uvx ctxfeed add ./src/auth.py
# 起 stdio MCP server,给 Claude Code / Cursor / Codex 消费
uvx ctxfeed mcp --repo /path/to/repo
# 在 Claude Code 里注册:
claude mcp add ctxfeed -- uvx ctxfeed mcp --repo /path/to/repo注册后,在 Claude Code 里问"auth middleware 在哪?"——ctxfeed 把全仓库摄入 GLM-5.2 的 1M 窗口,一次 MCP 往返返回带文件路径引用的答案。MCP 暴露三个工具:
工具 | 作用 |
| 全仓库入上下文 + 一次调用回答问题 |
| 列出会被摄入的文件 + layer + 缓存状态 |
| 单次查询 token 成本 vs Opus |
编程式 API:
from ctxfeed.cache_plan import CachePlan
with CachePlan.for_repo("/path/to/repo") as cp:
plan = cp.plan() # 缓存感知 ShardPlan
qr = cp.query("auth middleware 在哪?") # 全仓库一次往返
delta = cp.cost_delta() # vs Opus 的成本差
print(qr.answer, delta.savings_ratio_glm)
10 分钟从 git clone 到首屏可见结果:uvx ctxfeed init → uvx ctxfeed cost,看到两个"可星标"数字——文件数(1000+ vs 40)和单次成本 vs Opus。
环境变量 / 配置 | 类型 | 默认 | 含义 |
| str |
| GLM-5.2 API key(空 → dry-run 模式) |
| str |
| 别名,回退读 |
| str | — | MCP server 的仓库根(也可 |
| int |
| GLM-5.2 上下文窗口 |
| int |
| 跳过大于此值的文件 |
| str |
| SQLite 缓存键库路径 |
m1 ingest benchmark — 1000 文件摄入 GLM-5.2 1M 窗口 + repo-QA 对 200k-RAG 基线 kill-check
m2 shard + MCP — 缓存感知
ShardPlan+ stdio MCP server(query_repo/list_files)m3 ship CLI —
uvx ctxfeed init/add/cost+ 成本差 dashboard多供应商成本兜底(Kimi K3 / GLM 5.5 config stub)
ECC 级 agent-harness 集成 PR(dify / ECC 把 ctxfeed 作为 MCP 项目上下文后端)
vs ChatGPT Projects / Claude Code 200k 窗口
维度 | ctxfeed (GLM-5.2 1M) | ChatGPT Projects | Claude Code 200k |
文件上限 | ✓ 1000+ | ✗ 40 | 部分(按 token 截断) |
单次查询成本 | ✓ CN 长上下文定价 | — 套餐 | ✗ US per-token |
prefix-cache 折扣 | ✓ DeepSeek V4 兜底 | — | ✗ |
MCP 原生接入 agent | ✓ stdio | ✗ | 部分 |
企业合规/数据驻留 | ✗(CN 路由是硬停) | ✓ | ✓ |
企业合规买家不在目标内——CN 路由对他们是硬停,不是偏好(mvp_plan §6 out of scope)。
Related MCP server: mcplens
分享
ctxfeed — 把整个 1000+ 文件仓库塞进 GLM-5.2 的 1M token 窗口,喂给 coding agent 的 MCP 项目上下文后端。绕过 ChatGPT 的 40 文件上限,单次成本低于 Opus。https://github.com/SuperMarioYL/ctxfeedLicense + 贡献
MIT — 见 LICENSE。提 issue 或 PR:github.com/SuperMarioYL/ctxfeed/issues。
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceA local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.Last updated74615MIT
- Alicense-qualityBmaintenanceA local MCP server that provides AI coding assistants with semantic search capabilities over codebases. It indexes code using local embeddings and exposes tools for efficient code retrieval, saving tokens and improving response quality.Last updated314MIT
- AlicenseAqualityAmaintenanceAn MCP server giving coding agents context-window-aware code search and safe, atomic multi-file edits — built to cut token usage on large codebases without sacrificing correctness.Last updated3685MIT
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.Last updated375591MIT
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SuperMarioYL/ctxfeed'
If you have feedback or need assistance with the MCP directory API, please join our Discord server