laravel/boost

Organizational standardization with MCP files

Closed this issue · 4 comments

ahinkle commented

Laravel Package Version

1.0.17

Laravel Version

12.20.0

PHP Version

8.4

System Info

MacOS Sequoia

Description

When using Boost with Laravel Herd, it sets a SITE_PATH that’s hardcoded to my local system path where the project lives. How should this be handled in a team environment where developers have the project in different paths? Should this file be in .gitignore, or is there a better approach?

boost/src/Console/InstallCommand.php

Line 508 in 915d7d8

env: ['SITE_PATH' => base_path()]

mcp.json:

{
    "mcpServers": {
        "laravel-boost": {
            "command": "php",
            "args": [
                "./artisan",
                "boost:mcp"
            ]
        },
        "herd": {
            "command": "php",
            "args": [
                "/Applications/Herd.app/Contents/Resources/herd-mcp.phar"
            ],
            "env": {
                "SITE_PATH": "/Users/ahinkle/Sites/MyOrganization/MyProject"
            }
        }
    }
}

Steps To Reproduce

  1. Use Herd
  2. Sets site path to the installed project root
pushpak1300 commented

MCP configuration files should generally be excluded from version control since they often contain environment-specific settings. Many MCP clients use absolute paths or client-specific configurations that won't work across different development environments. However, if your MCP client uses relative paths that are portable across team members' setups, those configuration files can be safely committed to the repository.

@ashleyhindle should we put this in Readme ? guidelines can be added to git depending on everyone preference.

ahinkle commented

Yeah, that's what I was thinking too, but I wasn’t sure how the DX would play out since boost:install would not only add the MCP files, but reconfigure Boost, resulting in varying installations.

ashleyhindle commented

I do think we need to offer our recommendation in the README, or in the Boost docs site when we have it.

Agree the DX isn't great when we then need to ask every dev to run boost:install, and it might mess with guidelines again somehow 🤔 We kind of need boost:install-mcp which only does MCP based on boost.json config file?

What do we think is best for teams across the world?

ahinkle commented

Something like boost:install --only-mcp would work for our team.