dev.aieph由 aieph.dev 发布官方发布者v0.1.0更新于 Oct 24, 2026
Shared knowledge cache for AI coding agents — reuse an answer once it exists.
一个远程 MCP 服务器，让 AI 编程助手在联网搜索前先查询共享的编程问答缓存。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/dev.aieph%2Faieph/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"aieph": {
"type": "http",
"url": "https://aieph.dev/mcp"
}
}
}your fix, everyone's gain
aieph is a shared answer cache for AI coding assistants.
When an AI coding assistant is about to search the web, a small hook can quietly ask: "Does someone already have the answer?"
If the answer is already in the shared cache, aieph can return it right away — avoiding another trip to the web. If there is no answer, aieph simply gets out of the way.
MISS, timeout, or error? Nothing breaks. The original request continues as usual. That is the whole idea.
Your fix can become everyone's gain.
AI coding assistants often look up the same kinds of things:
The first person does the searching. The next person doesn't necessarily need to. aieph gives those answers a place to be shared, and as more people use it, the cache can gradually become more useful.
It's still early, so a cache hit is not guaranteed. Sometimes aieph simply won't have the answer yet — and that's perfectly fine.
aieph is designed to stay out of the way. There is no need to change how you work when the cache doesn't have something useful.
Claude Code can use aieph with a single PreToolUse hook for WebSearch and
WebFetch. A small setup looks like this:
Then, in ~/.claude/settings.json, the relevant hook can look like:
That's it.
Requirements: Node.js 18+. No account or API key is required.
Optional environment variables:
Cursor support is being prepared.
If aieph is no longer useful for you, removing the PreToolUse block is enough
to return to the original setup.
aieph is intentionally simple and transparent. Only the search query text is sent for matching. Nothing else is sent. There is no account to create and no personal profile to maintain. When there is no matching answer, the request passes through normally.
aieph also includes a small local-only memory CLI in cli/. It is
separate from the shared answer cache. The idea is simple: write a fact once,
and let connected assistants remember it later. This memory stays completely
local.
aieph is still growing. The shared cache is young, so there will be plenty of moments when it doesn't have an answer yet. That's intentional: aieph never needs to be perfect to be useful. A miss should feel exactly like there was no cache at all.
Over time, every useful answer someone discovers has the potential to help the next person.
your fix, everyone's gain.
MIT
来源：README.md，提交 1de4c7c
Look up the shared programming knowledge cache for error meanings, library usage, and how-tos. Do not send user code, files, or chat history—general questions only. Privacy: queries are PII-masked and logged anonymously. Details: aieph.dev/privacy
query必填sessionlanguage已满足适用检查项的 100%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
AI assistant │ │ "I'm about to search..." ▼ aieph │ ├── HIT → answer is already here │ └── MISS / timeout / error │ ▼ original searchgit clone https://github.com/tryaieph/aieph.git{ "hooks": { "PreToolUse": [ { "matcher": "WebSearch|WebFetch", "hooks": [ { "type": "command", "command": "node /path/to/aieph/hook/aieph-cache.mjs" } ] } ] }}AIEPH_API_BASELOOKUP_TIMEOUT_MS