Codex

This configuration connects Codex to the local akasha-mcp demonstration. Its current standalone memory is process-local; it does not establish durable memory in a dedicated Mind.

Configure the local process

Build or install the binary using Standalone MCP, then add this entry to ~/.codex/config.toml or the trusted project's .codex/config.toml:

[mcp_servers.minds_local_demo]
command = "/absolute/path/to/akasha-mcp"
args = ["--transport", "stdio", "--namespace", "local-demo", "--agent-id", "codex"]

Use an absolute executable path that exists on the host running Codex. Keep the name explicit so this demonstration is not confused with a production Mind.

Alternatively:

codex mcp add minds_local_demo -- /absolute/path/to/akasha-mcp \
  --transport stdio --namespace local-demo --agent-id codex

Codex supports command/args configuration for local stdio servers and provides codex mcp list and /mcp to inspect configured or active servers. See the current official Codex MCP documentation for client settings and tool policies.

Verify the actual tool call

Confirm that the server connects and advertises the expected tools. Ask Codex to recall a non-sensitive query and inspect the tool result. If you test remember followed by recall, keep the same server process alive.

A configured server entry does not prove persistence. Do not replace the command with your daemon's /v1/mcp/tools/call URL: that endpoint is an HTTP tool API, not a Streamable HTTP MCP session endpoint. For application-controlled durable memory, use HTTP tools.

Keep the host's normal tool approval controls. Retrieved memory remains data to consider, not instructions that override the current task.