AlembicPlugin — Runtime MCP para Codex
GxFn/AlembicPlugin
Memória local de projeto e ferramentas para Codex via MCP
Ver no GitHubMCP server que integra o Alembic ao Codex, fornecendo memória local do projeto (Recipes, verificações Guard, bootstrapping). É um runtime embarcado que habilita o Codex com contexto e ferramentas de projeto sem necessidade de setup adicional em cada sessão.
Instalação
npx convez-ai GxFn/AlembicPlugin1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Integração do Alembic ao Codex com contexto persistente
- Inicialização automática de projetos e bootstrap de conhecimento
- Verificação local e diagnóstico de workspace sem daemon adicional
Veredito

Um MCP server de infraestrutura focado em integração aprofundada com Codex. Recomendado para quem já usa Alembic e quer estender capacidades do Codex via plugin — não é ferramenta standalone.
README
A tradução para o português deste README ainda está na fila.
AlembicPlugin — Alembic Codex Plugin Runtime
This repository builds the Alembic plugin for Codex: a lightweight MCP
server that gives Codex local project memory (Recipes, Guard checks, project
knowledge bootstrap) without turning every chat into a setup session. It is
the embedded runtime artifact repository — the root package
(alembic-codex-plugin-runtime) is private and is never published to a
registry directly.
中文 · End-user install guide: plugins/alembic-codex/README.md
If you are looking for the full Alembic product (CLI, Dashboard, IDE
integrations), that lives in the main Alembic repository and is published as
alembic-ai on npm. This repository only owns the Codex plugin runtime.
Codex 插件
This repository owns the Codex plugin runtime, marketplace shell contract, MCP tool surface, and local verification flow for Alembic inside Codex. It does not publish the full Alembic product and it does not add a separate AI provider runtime; Codex remains the host agent, while this plugin provides local project memory, bootstrap, Guard, and status tools.
What runs where
- MCP server entry:
bin/codex-mcp.ts, built todist/bin/codex-mcp.jsand exposed as thealembic-codex-mcpbinary. Codex talks to this process over MCP; tool calls return cleanstructuredContent(ok,status,summary, optionalerror/meta, and tool-specific fields). Visible tool text is summary-only — hosts must not parse JSON out of text. - Startup model: Codex starts a lightweight shim first; diagnostics and
workspace status work without initializing the database. Init defaults to
Ghost mode. The per-workspace daemon (
bin/daemon-server.ts) is started or connected only when project knowledge, Guard, Dashboard handoff, bootstrap, or rescan actually need it. The embedded HTTP surface is pinned byCODEX_EMBEDDED_RUNTIME_REQUIRED_ROUTES(lib/runtime/runtime/EmbeddedRuntimeContract.ts). - Recommended first run inside Codex:
alembic_codex_diagnostics→alembic_codex_status→alembic_codex_init(if not initialized) →alembic_codex_bootstrapfor first project knowledge, oralembic_intent+alembic_primebefore coding once knowledge exists.
Delivery chain (channel → marketplace shell → pinned runtime)
channels/codex/channel.jsonis the Codex distribution entry; it names the marketplace manifest (.agents/plugins/marketplace.json) and the runtime package pin.plugins/alembic-codex/is the public installable marketplace shell (submodule →GxFn/AlembicCodex). Its MCP config startsbin/alembic-start.mjs; the shell ships no runtime code.- The shell installs the exact pinned npm runtime package
(
@gxfn/alembic-runtime, boundary inpackages/alembic-codex-runtime/) into the Alembic startup cache on first run and reuses the cache afterwards.
Users install via the Codex plugin marketplace:
codex plugin marketplace add GxFn/AlembicCodex --ref main
Release, version-pin alignment, tagging, and promotion are documented in
plugins/alembic-codex/RELEASE-PLAYBOOK.md.
How and when vendor/AlembicCore is refreshed (and how snapshot lag is
checked) is documented in AGENTS.md.
Development
npm install
npm run build # builds @alembic/core source first, then this repo
npm test # vitest suite
npm run lint # biome + boundary lints
@alembic/core resolves from the sibling checkout ../AlembicCore when
present (local development), otherwise from the vendor/AlembicCore snapshot
(scripts/local-source-paths.mjs). The vendor snapshot is refreshed by the
release flow, not edited by hand — see the release playbook.
Local Codex iteration:
npm run dev:codex-plugin:sync # sync built runtime into the Codex plugin cache
npm run dev:codex-plugin:reload # reload the plugin in a running Codex
npm run dev:codex-plugin:verify # verify the synced cache
Verification
npm run build:check # core + plugin type-check
npm run smoke:codex-plugin # end-to-end plugin smoke (required files, routes, MCP)
npm run verify:codex-plugin # plugin artifact verification
npm run verify:codex-channel # channel/marketplace alignment
npm run lint:repo-boundary # repository boundary lint
npm run release:check # aggregate release gate
Boundaries and governance
- Repository working rules, window responsibility, and automation gates:
AGENTS.md(andCLAUDE.mdfor Claude Code hosts). - Every remaining legacy compatibility path is tracked with an owner and a
concrete retirement condition in
docs/legacy-register.md. - Dashboard frontend source, build, and serving belong to Alembic/AlembicDashboard — this plugin only performs a daemon handoff.
Requirements
- Node.js ≥ 22
- better-sqlite3 (bundled)
License
MIT © gaoxuefeng