Codex can't enumerate tools for the laravel-boost mcp server.
What version of Codex CLI is running?
117
What subscription do you have?
Pro
Which model were you using?
gpt-5.4 high
What platform is your computer?
Darwin 25.4.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
iTerm2 build 3.6.9
What issue are you seeing?
Codex CLI 0.117.0 is detecting a local MCP server but caching it as having no tools.
Environment
- Codex version: 0.117.0
- Project: Laravel app with
laravel/boostandlaravel/mcp - MCP server configured in
~/.codex/config.tomlas:
[mcp_servers.laravel-boost]
command = "/opt/homebrew/bin/php"
args = ["artisan", "boost:mcp"]
cwd = "/Users/xxxx/src/webstack/cwics"
Observed behavior
- Codex UI shows
laravel-boostwithTools: (none) - Codex cache file
~/.codex/cache/codex_apps_tools/24f8a4dbd35e158afc9278429be4f359a5d156f9.jsoncontains:
{"schema_version":1,"tools":[]}
Important evidence
- Codex startup log shows MCP is enabled:
session_init.enabled_mcp_server_count=2
- The Laravel Boost MCP server works correctly when tested directly over stdio.
- Running an
initializefollowed bytools/listagainstphp artisan boost:mcpreturns a populated tool list with 15 tools, including:
application-info, database-schema, search-docs, tinker, etc.
Direct repro command
cat <<'EOF' | /opt/homebrew/bin/php artisan boost:mcp
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"debug","version":"1.0"}}}
{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}
EOF
Expected
- Codex should show the Laravel Boost tools and cache them correctly.
Actual
- Codex recognizes the MCP server exists, but caches the tool list as empty and the UI shows
Tools: (none).
What steps can reproduce the bug?
Uploaded thread: 019d43c2-5940-79d3-b4e9-d83d964e519a
What is the expected behavior?
It should have been able to enumerate and cache the tools for the mcp properly, but it persists tools: [].
Additional information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗