You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
mcpx: front codex-connectors-mcp, for OAuth-authenticated apps without mcpx doing OAuth #1982
Relocated from dezren39/darwin-nix#342 on 2026-10-28 (placement audit): mcpx's single source lives in developing-today/code (pkgs/mcpx); re-home tracked at #309. Original body below; issue references inside it are historical (dezren39/nix numbering).
Set up: install the Codex CLI (not installed here today), codex login, connect apps, then add it to mcpx's config (mcpx.config.nix in this repo) as a stdio upstream: npx -y @wileai/codex-connectors-mcp@latest with CODEX_CONNECTORS_ALLOW naming the apps, and probably CODEX_CONNECTORS_MODE=compact, since mcpx's own catalogue does the discovery.
Gets authenticated services today; does not replace #253.
Acceptance criteria
Codex CLI installed, codex login completed, and at least one app connected in Codex
codex-connectors-mcp is configured as a stdio upstream in this repo's mcpx config with CODEX_CONNECTORS_ALLOW naming the connected apps (and CODEX_CONNECTORS_MODE=compact unless a reason against is recorded)
A call through mcpx to one connected app succeeds end-to-end, demonstrating OAuth stayed entirely on the Codex side
Still live; externally blocked in part. Setup requires the Codex CLI and an interactive codex login, neither of which exists in this environment today — that step is Drew's (or a laptop session's), after which the mcpx config change is small.
Related:#346 (parent tracker), #253 (mcpx's own OAuth — this issue explicitly does not replace it), #345 (the authorization-server investigation, the other end of the same question).
Suggested approach: once the Codex login exists, treat the rest as a config-only change in mcpx.config.nix plus one end-to-end verification call.
Triage verdict (task 2357): CONFIRMED not implemented in the repo — and blocked on a Drew-only step before a fix packet can be scoped.
Verified at dezren39/nix main efd3161 plus a laptop probe (2026-10-28):
No trace of the connector on current main: git grep codex-connectors / CODEX_CONNECTORS on origin/main returns nothing, and mcpx.config.nix (the file the issue names) defines its upstreams (github, atlassian, datadog, context7, the fff family, …) with no codex-connectors-mcp stdio entry. Acceptance criteria 2 and 3 are unmet.
The body's premise has partly moved since filing ("install the Codex CLI (not installed here today)"): a laptop probe today finds /run/current-system/sw/bin/codex, codex-cli 0.160.0, and ~/.codex/auth.json present — so the CLI is installed and a Codex login exists. Acceptance criterion 1 is half met.
What is not evidenced: any app connected in Codex. ~/.codex/config.toml on the laptop shows no connector/app entries. CODEX_CONNECTORS_ALLOW must name the connected apps, and connecting an app is an OAuth consent only Drew can give in Codex — an agent cannot substitute for it, and guessing an ALLOW list would ship a config that fronts nothing.
Route: no follow-up fix packet enqueued deliberately — its scope cannot be pinned until Drew (1) connects at least one app in Codex and (2) names the apps for CODEX_CONNECTORS_ALLOW. Once that exists, the remaining work is the small config slice the body describes (stdio upstream in mcpx.config.nix, CODEX_CONNECTORS_MODE=compact, one end-to-end call through mcpx). Labelling status/blocked with that blocker named here.
Drew directed in main chat: build this directly, and wire in every app he has set up in ChatGPT/Codex — checking the account first rather than assuming none were connected.
Correction to the earlier triage verdict on this issue: the "no connected apps" finding was wrong. It read only the laptop's local ~/.codex/config.toml; the connections live on the account. Enumerating through the bridge itself (its codex_connectors tool, against the laptop's Codex login) shows 37 apps already connected: Airtable, ChatGPT Space, Codex Document Control, Context.dev, Context7, DigitalOcean, Dropbox, Engram, Exa, Firecrawl, GitHub, Gmail, Google Calendar, Google Drive, HAPI MCP Registry, Hotline, Lovable, Neon, OpenAI Platform, Parallel Search, Pets, Plugin Management, Railway, Remote Desktop Commander, Replit, Safety Settings, Search Service, Sites, Slack, Sprites, Stack Overflow For Agents, Supabase, tldraw, Todoist: To Do List & Calendar, Vercel, Walmart, Wolfram. No OAuth consent step remained for anyone — Drew had already connected them; Codex holds the OAuth, as this issue's design intended. (Cloudflare and CodeRabbit are enabled as Codex plugins but expose no connector tools through the bridge, so they are not in the list.)
Verified end-to-end (laptop, 2026-10-28):
Direct mode: bridge lists 1,234 tools (91 GitHub); live call github_get_profile → "Action completed."
Probe caveat worth keeping: drive the bridge sequentially. Piping all JSON-RPC messages in at once races the Codex app-server warm-up and calls are rejected with "Codex app-server rejected the request" — a probe artifact, not an account problem.
The issue body's suggested @latest does not resolve on npm (ETARGET, verified twice). The config pins @wileai/codex-connectors-mcp@0.1.1, the current release.
Config: PR #2068 adds the stdio upstream to .mcpx.json with CODEX_CONNECTORS_ALLOW naming all 37 apps and CODEX_CONNECTORS_MODE=compact; CODEX_CONNECTORS_WRITES stays at the bridge default (ask). JSON parses and mcpx.config.nix evaluates with the server carried through.
Acceptance criteria: (1) met — CLI installed, login live, 37 apps connected. (2) met by PR #2068, pending merge. (3) the bridge path is proven end-to-end in both modes; the final through-mcpx leg lands when the config activates at the next NixOS switch (the deployed config renders from this file via the flake). (4) unchanged — this remains complementary to the mcpx-native OAuth effort, not a replacement.
This issue can close when PR #2068 merges; the activation verification belongs to the switch checklist.
Activity
developing-today commentedon Oct 28, 2026
CODE-907
dezren39 commentedon Oct 28, 2026
History carried over from dezren39/darwin-nix#342 (verbatim, oldest first):
@dezren39 · 2026-10-27T11:12:53Z
Intake review — fleet monitor (2026-10-27)
Still live; externally blocked in part. Setup requires the Codex CLI and an interactive
codex login, neither of which exists in this environment today — that step is Drew's (or a laptop session's), after which the mcpx config change is small.Related: #346 (parent tracker), #253 (mcpx's own OAuth — this issue explicitly does not replace it), #345 (the authorization-server investigation, the other end of the same question).
Suggested approach: once the Codex login exists, treat the rest as a config-only change in
mcpx.config.nixplus one end-to-end verification call.@dezren39 · 2026-10-28T19:47:20Z
Triage verdict (task 2357): CONFIRMED not implemented in the repo — and blocked on a Drew-only step before a fix packet can be scoped.
Verified at dezren39/nix main
efd3161plus a laptop probe (2026-10-28):git grep codex-connectors/CODEX_CONNECTORSonorigin/mainreturns nothing, andmcpx.config.nix(the file the issue names) defines its upstreams (github,atlassian,datadog,context7, the fff family, …) with nocodex-connectors-mcpstdio entry. Acceptance criteria 2 and 3 are unmet./run/current-system/sw/bin/codex,codex-cli 0.160.0, and~/.codex/auth.jsonpresent — so the CLI is installed and a Codex login exists. Acceptance criterion 1 is half met.~/.codex/config.tomlon the laptop shows no connector/app entries.CODEX_CONNECTORS_ALLOWmust name the connected apps, and connecting an app is an OAuth consent only Drew can give in Codex — an agent cannot substitute for it, and guessing an ALLOW list would ship a config that fronts nothing.Route: no follow-up fix packet enqueued deliberately — its scope cannot be pinned until Drew (1) connects at least one app in Codex and (2) names the apps for
CODEX_CONNECTORS_ALLOW. Once that exists, the remaining work is the small config slice the body describes (stdio upstream inmcpx.config.nix,CODEX_CONNECTORS_MODE=compact, one end-to-end call through mcpx). Labellingstatus/blockedwith that blocker named here.dezren39 commentedon Oct 28, 2026
🤖 Agent note · picked up
2 remaining items
feat(mcpx): add codex-connectors upstream for the connected Codex apps (
dezren39 commentedon Oct 29, 2026
Owner direction + build record (2026-10-28)
Drew directed in main chat: build this directly, and wire in every app he has set up in ChatGPT/Codex — checking the account first rather than assuming none were connected.
Correction to the earlier triage verdict on this issue: the "no connected apps" finding was wrong. It read only the laptop's local
~/.codex/config.toml; the connections live on the account. Enumerating through the bridge itself (itscodex_connectorstool, against the laptop's Codex login) shows 37 apps already connected: Airtable, ChatGPT Space, Codex Document Control, Context.dev, Context7, DigitalOcean, Dropbox, Engram, Exa, Firecrawl, GitHub, Gmail, Google Calendar, Google Drive, HAPI MCP Registry, Hotline, Lovable, Neon, OpenAI Platform, Parallel Search, Pets, Plugin Management, Railway, Remote Desktop Commander, Replit, Safety Settings, Search Service, Sites, Slack, Sprites, Stack Overflow For Agents, Supabase, tldraw, Todoist: To Do List & Calendar, Vercel, Walmart, Wolfram. No OAuth consent step remained for anyone — Drew had already connected them; Codex holds the OAuth, as this issue's design intended. (Cloudflare and CodeRabbit are enabled as Codex plugins but expose no connector tools through the bridge, so they are not in the list.)Verified end-to-end (laptop, 2026-10-28):
github_get_profile→ "Action completed."codex_connector_call→github.get_profile→ "Action completed."@latestdoes not resolve on npm (ETARGET, verified twice). The config pins@wileai/codex-connectors-mcp@0.1.1, the current release.Config: PR #2068 adds the stdio upstream to
.mcpx.jsonwithCODEX_CONNECTORS_ALLOWnaming all 37 apps andCODEX_CONNECTORS_MODE=compact;CODEX_CONNECTORS_WRITESstays at the bridge default (ask). JSON parses andmcpx.config.nixevaluates with the server carried through.Acceptance criteria: (1) met — CLI installed, login live, 37 apps connected. (2) met by PR #2068, pending merge. (3) the bridge path is proven end-to-end in both modes; the final through-mcpx leg lands when the config activates at the next NixOS switch (the deployed config renders from this file via the flake). (4) unchanged — this remains complementary to the mcpx-native OAuth effort, not a replacement.
This issue can close when PR #2068 merges; the activation verification belongs to the switch checklist.
Merge pull request #2068 from developing-today/feat/mcpx-codex-connec…