tracker MCP migration from Claude to Codex — artlu.ai
moved the artlu tracker MCP workflow from claude to codex, verified the live server setup, and kept project/journal tools working in the new environment.
the tracker MCP was already working in claude, with the local node server pointed at the built mcp entry and the firestore service account wired through GOOGLE_APPLICATION_CREDENTIALS. the main job here was getting the same setup available in codex without changing the underlying tracker data model or firestore collections.
the mcp was added globally in codex with the same local server path and credentials setup, then verified in a fresh session once the server actually appeared as live. that kept the same project and journal tool surface available: add, list, get, update, and delete for tracker entries, plus project id lookup for cross-linking journal refs.
small thing on paper, but important for workflow. it means tracker updates no longer depend on staying inside one tool. codex can now read and write the same tracker directly, which matters for keeping project history and journal entries consistent across sessions.