Extend Codex functionality with MCP config

[pushpak1300]

Resolves #363.

We use the MCP shell installation strategy to add MCP config support as described in the Codex MCP CLI docs. This enables Codex to install MCP servers directly via CLI. Although Codex does not support project specific config yet, it now supports relative paths in the MCP config, which we leverage to add support for Laravel Boost.

Tested this with sail, herd and it work without any issues.

[jsandfordhughescoop]

@pushpak1300 - The only issue with it is that it sets the herd SITE_PATH as an absolute path however in my testing by setting it to * codex uses the relative path it was executed in.

[pushpak1300]

Thanks @jsandfordhughescoop for pointing that out. As Herd support global level mcp without env variable i've removed env key.

This is the standard configuration that works in most MCP clients. Make sure to replace YOUR-SITE-PATH with the base path to your Laravel project or remove the env key with the site path if you’re using the global installation.