-
-
Notifications
You must be signed in to change notification settings - Fork 0
MCP
If laravel/mcp is installed, the package
registers a local MCP server named minimax, so AI coding agents (Claude Code,
Codex, Cursor, …) can read the Minimax API directly.
How does this relate to Laravel Boost? Boost is itself an MCP server (exposing its own dev tools), not a client — it does not discover or absorb other Laravel MCP servers. Your AI agent is the client: point it at both the Boost server and this
minimaxserver and it sees both toolsets. They run as two independent processes; neither aggregates the other.
It ships three read-only tools:
| Tool | Arguments | Returns |
|---|---|---|
list-organisations |
— | Every org id + name the user can access. |
list-resource |
resource, org_id?
|
Rows from any org-scoped endpoint. |
find-record |
resource, id, org_id?
|
A single record by id. |
Each call uses the configured MINIMAX_ORG_ID unless you pass org_id.
php artisan mcp:start minimaxAdd the server to your MCP client config (.mcp.json / Claude Code):
{
"mcpServers": {
"minimax": {
"command": "php",
"args": ["artisan", "mcp:start", "minimax"]
}
}
}Pair it with MINIMAX_FAKE=true to let an agent explore the API shape with no
credentials.
The server is local (stdio) by default. To also serve it over HTTP for remote
clients, publish the routes and uncomment the Mcp::web(...) line — protect it
with auth middleware:
php artisan vendor:publish --tag=minimax-ai-routesWrite operations (issuing invoices, creating customers) have side effects, so they are intentionally left out of the MCP surface. Use the SDK in your own code for those.
Minimax SDK