Codex Project Memory
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Codex Project MemoryCheck for duplicate services before creating a new authentication module"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Codex Project Memory
Local repository memory for Codex. It indexes TypeScript/JavaScript structure into local SQLite, exposes compact MCP tools, and renders deterministic SVG/map frames.
What v0.2 does
Stores memory locally under
.codex/memory.Indexes TypeScript/JavaScript files, symbols, routes, modules, warnings and duplicate candidates.
Exposes MCP tools:
memory.agent,memory.head,memory.query,memory.duplicates,memory.frame,memory.refresh,memory.diff.Provides
pmem agent runas the project-local orchestration entrypoint.Produces deterministic SVG and map JSON. PNG export is best-effort and optional.
Related MCP server: Sverklo
Runtime Requirements
Node.js 20 or newer.
Codex with plugin and MCP support.
sharpis optional. If PNG generation is unavailable, SVG and map JSON remain the required visual outputs.
What v0.2 does not do
No embeddings or vector DB.
No cloud backend.
No dashboard.
No direct source-code modifications.
No required LLM in the core runtime.
Development
npm install
npm run build
npm test
node dist/cli/pmem.js --helpBefore packaging or sharing:
npm ci
npm run build
npm test
npm run marketplace:sync
node dist/cli/pmem.js --help
node dist/cli/pmem.js --version
npm pack --dry-runLocal repository setup
pmem init --json
pmem index --json
pmem render --json
pmem head --jsonMCP setup
Use .mcp.json with server name project-memory. The server command is
node scripts/bootstrap-mcp.mjs; on first start, the bootstrap installs runtime
dependencies in the installed plugin folder if they are missing, then starts
dist/mcp/server.js.
Codex Plugin Distribution
This repository is a single-plugin Codex marketplace root. The marketplace file
is .agents/plugins/marketplace.json, and its plugin entry points at
./plugins/codex-project-memory.
Before sharing changes, regenerate the distributable plugin folder:
npm run build
npm run marketplace:syncFrom a public or private Git repository:
codex plugin marketplace add owner/codex-project-memory --ref mainFrom a local clone:
codex plugin marketplace add /absolute/path/to/codex-project-memoryAfter adding the marketplace, open the Codex Plugin Directory, select
Codex Project Memory, install the plugin, and start a new thread. On first
MCP startup the plugin runs npm ci --omit=dev inside the installed plugin
folder so users do not need to prepare node_modules manually. That first
startup needs access to the npm registry or an already-warm npm cache.
More detail: docs/MARKETPLACE_SHARING.md.
This repository includes:
.agents/plugins/marketplace.jsonplugins/codex-project-memory/.codex-plugin/plugin.json.mcp.jsonskills/repo-memory/SKILL.mdbuilt runtime under
dist/afternpm run buildPRIVACY.mdSECURITY.mdCHANGELOG.md
Supported project lifecycle
Codex app plugin validation does not currently support plugin-declared hooks. The plugin uses a supported replacement: implicit skill invocation plus MCP tools. On project work, Codex should call memory.head, use memory.query before edits, use memory.duplicates before new artifacts, and call memory.refresh after source changes.
In v0.2 the preferred entrypoint is memory.agent, or the CLI equivalent:
pmem agent run "<intent>" --json
pmem agent run "<intent>" --phase pre_create --kind service --module <moduleId> --name <ProposedName> --jsonDuplicate guard
Before creating services, controllers, DTOs, routes, tables, modules, repositories, adapters, jobs or utilities, run:
pmem duplicates --kind service --module <moduleId> --name <ProposedName> "<intent>" --jsonDemo Walkthrough
From a copy of test/fixtures/nest-basic after npm run build:
node /path/to/MemoryCodex/dist/cli/pmem.js init --json
node /path/to/MemoryCodex/dist/cli/pmem.js doctor --json
node /path/to/MemoryCodex/dist/cli/pmem.js scan --json
node /path/to/MemoryCodex/dist/cli/pmem.js index --json
node /path/to/MemoryCodex/dist/cli/pmem.js render --json
node /path/to/MemoryCodex/dist/cli/pmem.js head --json
node /path/to/MemoryCodex/dist/cli/pmem.js agent run "Aggiungi controllo che impedisca l'apertura del tornello se l'abbonamento e sospeso." --json
node /path/to/MemoryCodex/dist/cli/pmem.js query "Aggiungi controllo che impedisca l'apertura del tornello se l'abbonamento e sospeso." --visual --json
node /path/to/MemoryCodex/dist/cli/pmem.js agent run "AccessValidationService / verifica diritto accesso" --phase pre_create --kind service --module access --name AccessValidationService --json
node /path/to/MemoryCodex/dist/cli/pmem.js duplicates --kind service --module access --name AccessValidationService "AccessValidationService / verifica diritto accesso" --json
node /path/to/MemoryCodex/dist/cli/pmem.js frame current --json
node /path/to/MemoryCodex/dist/cli/pmem.js refresh --changed-only --json
node /path/to/MemoryCodex/dist/cli/pmem.js diff --jsonThe duplicate command should return risk: "high" and verdict: "extend_existing_artifact" for AccessService.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/takaok5/codex-project-memory'
If you have feedback or need assistance with the MCP directory API, please join our Discord server