Skip to content

fix(mcp): use absolute path for Codex setup - #685

Merged
dmtrKovalenko merged 1 commit into
dmtrKovalenko:mainfrom
apanasenko-oai:codex/fix-codex-mcp-setup-path
Jul 17, 2026
Merged

dmtrKovalenko merged 1 commit into
dmtrKovalenko:mainfrom
apanasenko-oai:codex/fix-codex-mcp-setup-path

Conversation

@apanasenko-oai

@apanasenko-oai apanasenko-oai commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Why

Codex Desktop may not inherit the interactive shell's PATH. The installers currently recommend:

codex mcp add fff -- fff-mcp

This can leave fff configured but unavailable because Codex cannot resolve fff-mcp.

What changed

  • Update the macOS/Linux and Windows installers to register the installed binary using its quoted absolute path.
  • Add Codex setup examples for Homebrew and the one-line installer.
  • Document the resulting ~/.codex/config.toml entry and restart requirement.

Verification

Confirmed that an installation path containing spaces produces:

codex mcp add fff -- "/private/tmp/fff path/bin/fff-mcp"

Also verified the Homebrew command creates:

[mcp_servers.fff]
command = "/opt/homebrew/bin/fff-mcp"

and successfully initializes the MCP server and performs a repository grep.

@dmtrKovalenko
dmtrKovalenko merged commit 073698c into dmtrKovalenko:main Jul 17, 2026
51 of 52 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants