Support for Other Agents

[compgeniuses]

while installing i am prompted for this, however there are alot more agents in existed today, from Kiro, Trae, OpenCode, Cline, Kilo Code, RooKode, Warp.dev among others, i am not sure how the context are implemented for using non supported agents.

[jefsev]

Windsurf please

[compgeniuses]

i had to install using
.\artisan.ps1 boost:install --no-interaction

then created a docuemntation for kiro to utilize, for kiro case.

[nikitabuida]

• Gemini Code Assist and Gemini CLI

[voedito]

For Gemini CLI I just added this in my settings.json file and it works perfect.

"mcpServers": { "laravel-boost": { "command": "php", "args": ["./artisan", "boost:mcp"], "cwd": "D:\\Project\\Gemini\\App", "timeout": 30000, "trust": false } }

Working dir: "D:\Project\Gemini\App"

[redamakarem]

Can we please add support to:
windsurf
TRAE
Thanks

[Ale1x]

Kiro + trae, please!

[fanpero87]

I manually added the MCP server to Warp terminal like this:

{
  "laravel-boost": {
    "command": "php",
    "args": [
      "./artisan",
      "boost:mcp"
    ],
    "env": {},
    "working_directory": "/path/to/laravel/project"
  }
}

I suppose every time you want to work on a project, you would have to manually change the path under the MCP settings on Warp.

[ashleyhindle]

Related to:

• Trae - #39
• Zed - #86
• Amazon Q Chat - #162
• Windsurf - #87
• Gemini CLI - #123

[vesper8]

Pretty pretty please add support for Roo Code https://roocode.com/

[carbtest]

For Gemini CLI I just added this in my settings.json file and it works perfect.

"mcpServers": { "laravel-boost": { "command": "php", "args": ["./artisan", "boost:mcp"], "cwd": "D:\\Project\\Gemini\\App", "timeout": 30000, "trust": false } }

Working dir: "D:\Project\Gemini\App"

I assume you are running this on local windows env. how would i enable Gemini code assist in a linux env?

[lewis-hamer]

OpenAI Codex

[InTheCloudDan]

Please add Qodo Gen support.

[pushpak1300]

So Recently https://agents.md/ has been released and i think for guidelines we can support Agent.md for Codex, Cursor, Roo Code, Amp and Factory.

[nikspyratos]

So Recently https://agents.md/ has been released and i think for guidelines we can support Agent.md for Codex, Cursor, Roo Code, Amp and Factory.

Came here to comment this. We're rapidly entering an era where we now need standardisation of agent behaviour, just like we needed standardised protocols for agents to use which ended up with the creation of MCP.

A symlink/shortcut, approach may also work for agents that don't yet support it, or adding instructions to go read the AGENTS.md file in other agent files.

Claude Code directly supports telling it to read other files in CLAUDE.md, for example.

[andreilungeanu]

feat: add Roocode code environment detection and integration (#186)
feat: add Cline code environment detection and integration (#187)
feat: add KiloCode environment detection and integration (#188)

I think AGENTS.md should remain a user decision. Personally, I prefer the flexibility of keeping AGENTS.md separate and having Laravel Boost as an additional set of rules.

The “one file fits all” idea feels a bit like an overreach, since different projects and teams may want to maintain their own conventions. Since agents allow having their own sets of rules, it’s safe to use multiple tools in the same project, each with different rules, instead of forcing everything into a single file.

[pushpak1300]

Actually, I’m more in favor of standardisation(AGENTS.md) Since there's no hard limit on the number of agents we can maintain or support, we don’t need to go out of our way to support everything. Instead, we can just stick to a standard approach, and if someone wants a different setup, they’re free to do that on their end like using a symlink or something.

[Ale1x]

Actually, I’m more in favor of standardisation(AGENTS.md) Since there's no hard limit on the number of agents we can maintain or support, we don’t need to go out of our way to support everything. Instead, we can just stick to a standard approach, and if someone wants a different setup, they’re free to do that on their end like using a symlink or something.

+1

[andreilungeanu]

I see the value in AGENTS.md, but we should build on what agents already offer instead of forcing a single approach. Most agents already support multiple rule sets, so Laravel Boost and AGENTS.md can safely coexist.

Also, AGENTS.md is just one piece (guidelines) — we still have MCP configuration, which makes this more complex and worth deeper thought. For now, I value flexibility over enforcing “standards” that aren’t really standards yet. (Laravel way)

[marvix]

Zed please!

[MuhammadQuran17]

Windsurf please

I have configured it for Windsurf like:

{
    "mcpServers": {
      "laravel-boost": {
        "command": "bash",
        "args": [
          "-c",
          "cd /home/xmsi/documents/ai_double_check_laravel && ./vendor/bin/sail php artisan boost:mcp"
        ]
      }
    }
  }

[calebsmithdev]

I've been using Codex for my project this week and I am curious how others are handling Codex. It seems like their MCP integration is more of a global setting, rather than a project setting. So something like this can be more of a pain if I am dealing with multiple Laravel projects using Boost. At least I think I am understanding that correctly?

[mcp_servers.laravel-boost]
command = "/Users/USERNAME/Library/Application Support/Herd/bin/php"
args = ["/Users/USERNAME/Herd/PROJECT/artisan", "boost:mcp"]

[DNA]

Using Laravel Boost with Zed was pretty straightforward, just needed to add this on my settings:

  "context_servers": {
    "laravel-boost": {
      "source": "custom",
      "command": "php",
      "args": ["artisan", "boost:mcp"],
      "env": {}
    }
  }

[mwamodo]

I've been using Codex for my project this week and I am curious how others are handling Codex. It seems like their MCP integration is more of a global setting, rather than a project setting. So something like this can be more of a pain if I am dealing with multiple Laravel projects using Boost. At least I think I am understanding that correctly?

[mcp_servers.laravel-boost]
command = "/Users/USERNAME/Library/Application Support/Herd/bin/php"
args = ["/Users/USERNAME/Herd/PROJECT/artisan", "boost:mcp"]

You don't have to put the full path. Config below works for me, on codex CLI only. On the codex ide plugin it always errors with "MCP client for laravel-boost failed to start: request timed out"

[mcp_servers.laravel-boost]
command = "php"
args = ["artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

[dstrickler]

I would love to see a step-by-step guide on how to get this running with Warp.

[jpcaparas]

When using Laravel Sail, run docker ps --format '{{.Names}}' and get the name of your laravel/web container, e.g.

➜  app git:(main) docker ps --format '{{.Names}}'
app-laravel.test-1
app-meilisearch-1
app-selenium-1
app-redis-1
app-pgsql-1
app-mailpit-1

In this case, it's app-laravel.test-1.

Then, add this to your config.toml

[mcp_servers.laravel-boost]
command = "docker"
args = ["exec", "-i", "app-laravel.test-1", "php", "/var/www/html/artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

[Uhasith]

Bug Report: Laravel Boost MCP not accessible in Codex Chat But Working inside Codex CLI

Description

Codex chat reports that it cannot access Laravel Boost MCP tools (e.g., search-docs, tinker, database-query).
The MCP server does not appear to be registering when running inside Codex. @ashleyhindle @mwamodo

MCP client for `laravel-boost` failed to start: request timed out

Configuration

My config.toml contains:

[mcp_servers.laravel-boost]
command = "php"
args = ["artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

[pushpak1300]

Bug Report: Laravel Boost MCP not accessible in Codex Chat But Working inside Codex CLI

Description

Codex chat reports that it cannot access Laravel Boost MCP tools (e.g., search-docs, tinker, database-query). The MCP server does not appear to be registering when running inside Codex. @ashleyhindle @mwamodo

MCP client for `laravel-boost` failed to start: request timed out

Configuration

My config.toml contains:

[mcp_servers.laravel-boost]
command = "php"
args = ["artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

As Codex CLI works in your current working directory (cwd), it knows which MCP server to run. However, Codex Extension runs in the VSCode context, so you have to explicitly mention the path to artisan.

[mcp_servers.laravel-boost]
command = "php"
args = ["<complete-path>/artisan", "boost:mcp"]
transport = "stdio"

That's one of the reason to support MCP for codex is very tricky 😅

[Uhasith]

Bug Report: Laravel Boost MCP not accessible in Codex Chat But Working inside Codex CLI

Description

Codex chat reports that it cannot access Laravel Boost MCP tools (e.g., search-docs, tinker, database-query). The MCP server does not appear to be registering when running inside Codex. @ashleyhindle @mwamodo
MCP client for `laravel-boost` failed to start: request timed out

Configuration

My config.toml contains:
[mcp_servers.laravel-boost]
command = "php"
args = ["artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

As Codex CLI works in your current working directory (cwd), it knows which MCP server to run. However, Codex Extension runs in the VSCode context, so you have to explicitly mention the path to artisan.

[mcp_servers.laravel-boost]
command = "php"
args = ["<complete-path>/artisan", "boost:mcp"]
transport = "stdio"

That's one of the reason to support MCP for codex is very tricky 😅

Is there any workaround to solve this mate ? This is also not working @pushpak1300

[mcp_servers.laravel-boost]
command = "php"
args = ["/Users/USERNAME/Sites/site-name/artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

[pushpak1300]

@Uhasith, the above configuration is working correctly for me in the Codex extension. You could also try using an absolute path for the PHP executable.

[Uhasith]

@Uhasith, the above configuration is working correctly for me in the Codex extension. You could also try using an absolute path for the PHP executable.

Thank You !!! @pushpak1300. I just wanted to let you know that this works for me.

Step 1

which php => get command path (php)

Step 2

pwd => get current directory path

[mcp_servers.laravel-boost]
command = "/Users/USERNAME/Library/Application Support/Herd/bin/php"
args = ["/Users/USERNAME/Sites/site-name/artisan", "boost:mcp", "--no-interaction"]
transport = "stdio"

[pushpak1300]

We’re currently working on the feature of Boost, so anyone can extend Boost and provide their own IDE/AI agent integration. Supporting multiple agents and IDEs is pretty impossible. Here’s the MR: #280. In the meantime, if any of you can test the integration with your own standalone package, that would be great and we could improve the integration.

Thanks.

[pushpak1300]

We’ve just released a new version of Boost (v1.4.0). With this version, you can now extend Boost to add your own packages and integrate with your preferred IDEs and AI agents.

👉 v1.4.0 Release Notes
👉 Guide: Adding support for other IDEs & AI agents

Thanks.

[GoneTone]

This package add Windsurf support to Laravel Boost, enabling seamless integration with both Windsurf Editor and Windsurf JetBrains Plugin.

https://github.com/GoneTone/laravel-boost-windsurf-extension

After running php artisan boost:install, you'll see two new options:

• windsurf - For Windsurf Editor
• windsurf_jetbrains_plugin - For Windsurf JetBrains Plugin (PhpStorm, etc.)

When switching between Laravel projects, simply run php artisan boost:update. This automatically updates your Windsurf MCP configuration to point to the correct project path, saving you from manual configuration.