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