Add Unforgit as a candidate MCP registry/marketplace listing

Open 💬 0 comments Opened Jul 9, 2026 by MiguelMedeiros

What variant of Codex are you using?

CLI

What feature would you like to see?

Please consider adding a documented/curated MCP registry or marketplace path for third-party MCP servers, and include Unforgit as a candidate repository-memory MCP server when that registry becomes available.

Unforgit: https://github.com/MiguelMedeiros/unforgit
Icon: https://raw.githubusercontent.com/MiguelMedeiros/unforgit/main/docs/unforgit-icon.png

Unforgit is a local-first repository memory system for AI coding agents. It gives Codex durable project memory for decisions, conventions, gotchas, and playbooks.

Codex project integration is already supported by Unforgit:

npm install -g unforgit
cd your-project
unforgit init --ide codex

Generated files:

  • .codex/config.toml
  • AGENTS.md

Generated MCP config:

[mcp_servers.unforgit]
command = "unforgit-mcp"
args = []

Additional information

Available MCP tools include:

  • unforgit_recall
  • unforgit_add
  • unforgit_curate
  • unforgit_embedding_recall
  • unforgit_health
  • unforgit_sync_status
  • consolidation/link/history tools

The MCP server discovers .unforgit/unforgit.yaml by walking up from the working directory and loads the repository .env automatically. Secrets are not stored in MCP config.

Related context: #25750 discusses MCP Server Registry Discovery. This request is intentionally framed as a registry/listing request rather than a Codex CLI bug.

Verification from the Unforgit repo:

  • pnpm test -> 224 tests passed
  • pnpm build -> passed
  • pnpm lint -> 0 errors

View original on GitHub ↗