Codex + remote MCP
Keep the work.
Beyond the session.
Save the useful pieces of a Codex session as objects you own. Retrieve them in a new session—or from another connected agent—without treating chat history as your database.
Open-source core. Hosted Free plan. No card needed to start.
{
"key": "projects/app/decision",
"kind": "reference",
"labels": [
"app"
],
"value": {
"decision": "Keep authentication separate from store access keys."
},
"searchable_text": "App decision: keep authentication separate from store access keys"
}Illustrative object input—not a live account or tool result.
“Save that decision under projects/app/decision.”
projects/app/decision“Retrieve projects/app/decision before we continue.”
get_object returns the original saved valueAdd a remote MCP server
Create a Simple Agent Store account, open Get started and create an access key named for your Codex client. Select Codex to get the server configuration for the remote Streamable HTTP endpoint. Follow your client’s setup and approval flow.
The endpoint is https://www.simpleagentstore.com/api/mcp. Its access key is separate from your account login and only reaches your own stored objects. Keep credentials outside source control and use the workspace to revoke a key if a client or machine is no longer trusted.
Separate store results from workspace context
A repository, a prior chat and a connected store are different sources. For a saved-note request, tell Codex to retrieve from Simple Agent Store rather than infer from workspace files. For a save, it should call store_object and only report success after a successful tool result.
Check the data viewer after the first write. Then start a fresh session and fetch the same key. For “all my notes,” use list_objects with a note filter and follow all cursors; for a topic, search concise words and get the selected full objects.
Keep project handoffs small and concrete
Store a decision, a next action or a reference link rather than an entire source tree. JSON values, labels, versions and timestamps make these objects inspectable. Your repository remains the source of truth for code; the store holds explicit context you want to carry between sessions.
Optional routing guidance can make ordinary save requests easier for an agent to recognize. It is not a background sync service and cannot guarantee that every client will select the tool. Permissions, client support and checking persisted data remain part of the setup.
Three steps to a useful store.
- 01
Create a Codex access key
Use Get started in your account. Copy the credential securely; the complete key is shown once.
- 02
Connect and approve tools
Choose Codex setup, configure the remote MCP server and confirm the five storage tools are available.
- 03
Test a fresh-session read
Save a project reference, inspect it in the viewer, then retrieve the exact key in a new session.
A few practical questions.
Is this the same as Codex’s workspace memory?
No. Simple Agent Store is a separate object store. Only successful explicit writes create stored objects, and retrieval needs a store tool call.
Can I use it without MCP?
Yes. The conventional REST API exposes the same five operations using the same account-owned access keys and limits.