
Worldku Memory
com.worldku由 worldku.com 發布官方發布者v0.1.0更新於 Oct 24, 2026
Save AI conversations into your Worldku memory and recall them from any MCP client.
概覽
Worldku Memory 是託管的 MCP 伺服器,可把 AI 對話存進 Worldku 記憶帳戶,並讓助理日後搜尋與回想這些內容。
- 可以做什麼
- 瀏覽最近的記憶,每筆一行
- 對已儲存的記憶做語意搜尋
- 依時間範圍、類型或來源篩選並分頁回想記憶
- 儲存目前對話紀錄,交由非同步記憶擷取處理
- 在用戶端支援 Tasks 擴充時輪詢非同步儲存任務
- 適用情境
- 當你希望助理在 Claude Code、claude.ai、ChatGPT、Codex 或 Gemini CLI 等不同用戶端之間保留長期記憶,並在新工作階段取回相關舊脈絡時使用。
- 執行需求
- 需要遠端 Streamable HTTP 端點,無須本機安裝。必須驗證:支援 OAuth 的用戶端在 worldku.com 登入 OAuth 2.1,或使用以 Authorization Bearer 標頭傳送的 Worldku 存取金鑰(可在 worldku.com 的 Memory manager → AI tools 產生)。需要 Worldku 帳戶;所有方案(含免費版)都包含 MCP 存取。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Worldku Memory,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/com.worldku%2Fmemory/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"worldku-memory": {
"type": "http",
"url": "https://mcp.worldku.com/mcp"
}
}
}README
worldku-mcp
The official MCP server for Worldku memory. Save AI conversations into your Worldku memory and recall them back — from Claude Code, claude.ai, ChatGPT, Codex, Gemini CLI, or any other MCP client.
Full setup guide: worldku.com/docs/mcp — step-by-step instructions for every client, authentication details, and troubleshooting. The same page in raw Markdown for AI agents: worldku.com/docs/mcp.md.
The fastest way to set up: paste this into your AI tool and let it walk you through —
I want to give you long-term memory with Worldku. Read https://www.worldku.com/docs/mcp.md and walk me through connecting it, in your own words.
Hosted service. The public endpoint is https://mcp.worldku.com/mcp. This
repository is the open access layer only: the memory extraction pipeline, prompt
rules, and platform services run on Worldku's infrastructure. Self-hosting this
worker will not give you a working service — it exists for transparency and
review, and connects to backends that require Worldku credentials.
Tools
All tools fire only on your explicit ask — the tool descriptions instruct the model never to call them from ambient association. Saved transcripts go through Worldku's normal import pipeline: extraction runs asynchronously and new memories land in your memory workbench marked unread. Re-saving the same conversation is deduplicated server-side; extending a previously saved conversation appends only the new tail.
Connecting
Two authentication routes:
- OAuth 2.1 — claude.ai and ChatGPT need no key at all: point them at the server URL and sign in at worldku.com when prompted.
- Access key — CLI clients use a
wk_mcp_…key, minted at worldku.com → Memory manager → AI tools. The key is shown once at mint time; up to 20 keys per account, each independently revocable.
Claude Code
To keep the key out of the config file, export WORLDKU_MCP_KEY in your shell
profile and use single quotes: --header 'Authorization: Bearer ${WORLDKU_MCP_KEY}'.
claude.ai (web, desktop, mobile)
Settings → Connectors → Add → Add custom connector →
https://mcp.worldku.com/mcp → sign in at worldku.com. No key needed.
ChatGPT (web)
Enable Developer mode (Settings → Security and login), then create an app at chatgpt.com/plugins with the server URL and OAuth authentication. Sign in at worldku.com when prompted.
Codex CLI
Gemini CLI
Any other MCP client
Any client that supports Streamable HTTP with a custom header works:
- URL:
https://mcp.worldku.com/mcp - Header:
Authorization: Bearer wk_mcp_YOUR_KEY
The config field holding the URL varies by client (url for most, httpUrl
for Gemini CLI, serverUrl for some others) — a wrong field name usually makes
the client ignore the server silently. More examples in examples/
and in the full guide.
Protocol
- Native MCP revision 2026-07-28 (stateless Streamable HTTP): per-request metadata, no sessions, no SSE streams — every response is a single JSON object.
- Dual-era: the 2025-11-25 initialize-handshake era is also served (still statelessly — no session ids, no SSE), because that is what current-generation clients speak. This leg will be dropped once the client ecosystem moves to 2026-07-28.
server/discover,tools/list,tools/call, and the Tasks extension (tasks/get/tasks/update/tasks/cancel) for async save polling. Clients that do not declare the extension get synchronous receipts instead.- OAuth 2.1 resource server per the MCP authorization spec: RFC 9728 protected
resource metadata at
/.well-known/oauth-protected-resource, audience-bound opaque tokens,memory:read/memory:writescopes. The authorization server (worldku.com) supports Client ID Metadata Documents and PKCES256. - Discovery (SEP-2127 experimental): Server Card at
/mcp/server-card, AI Catalog at/.well-known/ai-catalog.json.
Limits
- 200 reads and 50 saves per user per day (anti-abuse caps, reset at 00:00 UTC).
- 10 MB per request.
- Reads and saves each book one usage action on your Worldku account. MCP access is included with every Worldku plan, including Free.
Development
Deployment (Cloudflare Workers) is done by the Worldku team — see
wrangler.toml for the binding surface (no secrets live in this repo).
License
來源:README.md,提交 7e8ec36
工具
0版本歷史
1- v0.1.0最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分