[AI-774] docs: fix Codex MCP config path for kcap mcp flows

[realtonyyoung]

What

The ### Flows MCP server (for agents) section told Codex users to add kcap mcp flows to ~/.config/codex/mcp_servers.toml under a bare [kcap-flows] table. Both are wrong:

• The actual Codex config (CLI and the desktop app) is ~/.codex/config.toml — ~/.config/codex/ does not exist.
• MCP servers must live under a [mcp_servers.<name>] table, not a bare [kcap-flows] table.

Verified against a real Codex desktop install (/Applications/Codex.app), whose ~/.codex/config.toml already configures its own MCP servers via [mcp_servers.node_repl].

Change

Doc-only. Corrects the path/table and adds a note that the desktop app launches MCP servers without the user's shell PATH, so an absolute command path is needed.

🤖 Generated with Claude Code

[linear-code]

AI-774

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[alexeyzimarev]

/agentic_review

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Inconsistent Codex MCP docs ✓ Resolved 🐞 Bug ≡ Correctness

Description

README.md now documents Codex MCP server config as ~/.codex/config.toml under
[mcp_servers.<name>], but other user-facing docs/help still reference
~/.config/codex/mcp_servers.toml with bare [kcap-*] tables. This leaves conflicting setup
instructions in the repo and will still send some users to the wrong file/table.

Code

README.md[R298-301]

+# Codex (CLI or desktop app) — add to ~/.codex/config.toml:
+# [mcp_servers.kcap-flows]
+# command = "kcap"           # use an absolute path (e.g. /opt/homebrew/bin/kcap) for the
+# args    = ["mcp", "flows"] # desktop app, which launches MCP servers without your shell PATH

Evidence

The README change now points Codex users at ~/.codex/config.toml under [mcp_servers.kcap-flows],
but other docs/help still explicitly instruct ~/.config/codex/mcp_servers.toml and bare tables,
which conflicts with the updated README guidance.

README.md[294-302]
kcap/README.md[7-8]
src/Capacitor.Cli.Core/Resources/help-mcp.txt[56-60]
src/Capacitor.Cli.Core/Resources/help-mcp.txt[75-78]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The PR updates Codex MCP configuration instructions in `README.md`, but other documentation/help resources still reference the old Codex config path/table shape (`~/.config/codex/mcp_servers.toml` and bare tables). This creates conflicting guidance.

### Issue Context
Users may follow `kcap/README.md` or CLI help text instead of the root README, and will still be told to edit a non-existent/incorrect Codex config location.

### Fix Focus Areas
- kcap/README.md[7-8]
- src/Capacitor.Cli.Core/Resources/help-mcp.txt[56-60]
- src/Capacitor.Cli.Core/Resources/help-mcp.txt[75-78]

### Expected change
Update those sections to match the corrected Codex config format:
- Config file: `~/.codex/config.toml`
- Table: `[mcp_servers.<name>]` (e.g. `[mcp_servers.kcap-flows]`)
- Consider mirroring the README note about needing an absolute `command` path for the desktop app (if that help text is intended to cover the desktop app as well).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---