OAKOAK/memory
Dashboard
DocumentationGet started
OAK.memory

Connect Codex

Follow the steps for your desktop app or CLI to connect OAK memory.

1. Prepare your account and store

Sign in to OAK and prepare a store. Keep using your existing account if you have one. Connection menus may depend on your AI plan and organization policy.

Sign in to OAK

2A. Connect in the desktop app

Open Settings → MCP servers → Add server. Use oak-memory as the name, Streamable HTTP as the transport, and the address below. Save, Restart, then select Authenticate to sign in. Menu names may vary by app version.

MCP server URL
https://www.openaikits.com/api/mcp

2B. Connect in the CLI

Run these commands in order. If the name already exists, inspect codex mcp list first and preserve its configuration. Sign in to OAK in the browser opened by the login command. The app and CLI share local connection settings; configure only one.

Codex CLI
codex mcp add oak-memory --url https://www.openaikits.com/api/mcp
codex mcp login oak-memory

4. Check the connection with a real request

In a new chat, use /mcp to check that OAK memory is enabled, then send the prompt below. Confirm the store and memory list through real tool calls.

Connection check prompt
In connected OAK memory, use currentMemoryStore to check the store name and my permissions, then listMemories to show the memory list. Do not use semantic search or write tools.

Using memory day to day

If something does not work

If Authenticate remains, first try an actual lookup in a new chat. If that fails too, authenticate again in the app or run codex mcp login oak-memory. Consult the official guide if your app version or organization policy changes the menus.

Official connection guide

Change or disconnect your store

Revoke access in OAK connection settings. To switch stores or add write access, reconnect and consent to the intended store and permissions. Listing memories and checking the store do not use embedding credits. Semantic recall and saving memories require credits.

Documentation

Carry useful context into your next AI conversation. Create a private store, connect your assistant, and save important facts and decisions as memories.

Get started

Choose your service. Follow the steps for your environment, from setup to connecting your store.

Quickstart

Create a store, connect your assistant and save your first memory. The cloud service runs the database for you.

Using memory day to day

Once connected, talk naturally. Try remembering a preference, finding it in another conversation, and keeping it up to date.

Connect OAK memory to ChatGPT

Connect ChatGPT to your OAK store so you can recall memories across conversations. Follow these steps to get started.

Connect Claude Desktop

Connect OAK memory in Claude Desktop or claude.ai through your Claude account’s connector settings.

Connect Codex

Follow the steps for your desktop app or CLI to connect OAK memory.

Core concepts

Understand memories, stores and retrieval before connecting them to a longer workflow.

Connect Claude Code

Use a personal key and store profile to connect the OAK.memory plugin to hosted memory.

Share a memory store

Give collaborators access to a shared context while keeping each account’s identity and usage separate.

MCP tool reference

The cloud MCP endpoint exposes tools for store discovery, retrieval and memory changes. Your connection supplies the account and store context.

Commands and conversation examples

Recall, save and manage memory from your conversation. Slash commands belong to the Claude Code plugin; connected web apps use natural-language requests.

Usage tiers and limits

Understand which limits your account shares, how operation credits work and what to do when a request is refused.

Troubleshooting

Identify whether an issue comes from your connection, permissions, usage or the embedding service.

Local plugin setup

Run memory on your own machine instead of using a hosted cloud store. This has a separate database and setup process.

Guides

Use memory for personal preferences, everyday plans, shared team context and development work.