Worldku Memory

com.worldkuPublished by worldku.comOfficial publisherv0.1.0Updated Oct 24, 2026

Save AI conversations into your Worldku memory and recall them from any MCP client.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Worldku Memory is a hosted MCP server that saves AI conversations into a Worldku memory account and lets an assistant search and recall them later.

What you can do
  • Browse recent memories, one line each
  • Run semantic search over saved memories
  • Recall memories filtered by time range, type or source, with pagination
  • Save the current conversation transcript for asynchronous memory extraction
  • Poll async save tasks where the client supports the Tasks extension
When to use it
Use it when you want an assistant to keep long-term memory of past conversations across clients such as Claude Code, claude.ai, ChatGPT, Codex or Gemini CLI, and to pull relevant earlier context back into a new session.
Requirements
A remote Streamable HTTP endpoint; no local install. Authentication is required: OAuth 2.1 sign-in at worldku.com for OAuth-capable clients, or a Worldku access key sent as an Authorization Bearer header (mintable at worldku.com under Memory manager, AI tools). A Worldku account is needed; MCP access is included in every plan, including Free.
Before you install
The access key is a secret shown once at mint time; keep it out of config files where possible and revoke keys you no longer use. Saving sends the full conversation transcript to Worldku's hosted pipeline, where extraction runs asynchronously. Reads and saves each count as a usage action on the account, with daily caps of 200 reads and 50 saves per user. The repository is not self-hostable into a working service.

Installation

In SourceWeft

  1. Open Worldku Memory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.worldku%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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

ToolWhat it doesCost
memory_overviewMost recent memories, one line each (zero parameters)1 read
memory_searchSemantic search over your memories1 read
memory_recallFiltered recall: time range / type / source, paginated1 read
memory_saveSave the current conversation transcript for memory extraction1 save

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

bash
claude mcp add --transport http --scope user worldku https://mcp.worldku.com/mcp \  --header "Authorization: Bearer wk_mcp_YOUR_KEY"

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

bash
export WORLDKU_MCP_KEY=wk_mcp_YOUR_KEYcodex mcp add worldku --url https://mcp.worldku.com/mcp --bearer-token-env-var WORLDKU_MCP_KEY

Gemini CLI

json
// ~/.gemini/settings.json — note the httpUrl field name{  "mcpServers": {    "worldku": {      "httpUrl": "https://mcp.worldku.com/mcp",      "headers": { "Authorization": "Bearer wk_mcp_YOUR_KEY" }    }  }}

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:write scopes. The authorization server (worldku.com) supports Client ID Metadata Documents and PKCE S256.
  • 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

bash
pnpm installpnpm test        # vitestpnpm type-checkpnpm lint

Deployment (Cloudflare Workers) is done by the Worldku team — see wrangler.toml for the binding surface (no secrets live in this repo).

License

MIT

Source: README.md at commit 7e8ec36

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts