Connect Codex.

Move between coding tools without rebuilding your project memory. Codex can consult and update the same readable notes as your other clients.

Browser sign-in · CLI, IDE & local desktop

Start in MarkdownMem

Sign in to the memory desk, select or create a memory store, and open Connect an agent. Copy the exact endpoint. The examples use placeholder workspace and store names.

Set up your client

1. Run the commands below with the exact endpoint copied from your memory store. The login command starts browser authorization; no connection key is needed.
2. Sign in to MarkdownMem, review access, and return to Codex. Start a new session and use /mcp in the CLI to check the connected server.
3. Run the read check below. Local desktop and IDE clients using the same Codex host share its MCP configuration, so they can reuse the connection.

codex mcp add markdownmem --url https://markdownmem.com/mcp/workspaces/WORKSPACE/agents/STORE
codex mcp login markdownmem

A cloud task or another host needs its own configured connection. Current OpenAI documentation also covers ChatGPT desktop sessions backed by a local Codex host; ChatGPT web custom apps use the separate ChatGPT guide.

Check that it reads the right memory

Create /context.md in the browser with a harmless project fact. In your agent, ask:

Use MarkdownMem to read /context.md. Tell me the project fact it contains. Don't change any notes.

To check portability, connect a second client to the same store and ask it to read that note. To check writes, ask one client to save a small test note and confirm it appears in the web editor. Keep the client's usual tool approval controls enabled.

Tell the agent when to use memory

Before working, search MarkdownMem for relevant context. Read the matching notes. After finishing, update durable decisions and preferences. Don't save credentials or whole conversation transcripts.

Add this to your client's project instructions if you want it to apply in future sessions. Connecting an MCP server does not automatically import built-in memory or make every conversation save notes.

If something does not connect

• Copy the endpoint again: a different store path selects different memory.
• Complete the client’s sign-in action and check your account still has access to the store.
• For browser OAuth, remove any old Authorization header or expired key that would take precedence.
• For cloud or remote sessions, configure the connection in that environment; local settings may not carry over.
• If only the interactive editor is missing, check MCP Apps support. Text tools can work even when a host does not render the UI.

Browser OAuth acts with your account's current permissions. For a narrower, unattended connection, see store-scoped automation keys.

Current client references

Instructions reviewed September 6, 2026 against the sources below. These are configuration guides, not a claim that every client version, plan, or managed workspace has been certified.

• OpenAI MCP documentation