laravel-agent-mcp

Use to call the agent-mcp read-only tools from the shell with artisan, without registering an MCP server: run agent-mcp:tools to list tools, agent-mcp:schema <tool> to see its inputs, and agent-mcp:call <tool> '<json>' to invoke one, locally or against a remote app via AGENT_MCP_URL. Use for one-off calls, scripts, CI, when the agent-mcp MCP server is not registered in the client, or when deciding between a one-off CLI call and registering the server. Covers local vs remote mode, JSON input, stdout and stderr, exit codes, and --allow-tty for sensitive tools. Do NOT use for write operations; these tools are read-only. When the MCP server is registered in the client, follow the agent-mcp-investigation workflow instead.

Use when investigating a running Laravel application through the agent-mcp read-only MCP tools: inspect the live database schema, run read-only queries to find or count records, read application logs to diagnose a 500, exception, or failed job, check queue backlog, failed jobs, or Horizon, inspect cache or optimization state, or audit routes, schedule, events, config, env keys, and storage. Use whenever the answer depends on live runtime state rather than source code, even when the user does not name the tools. Do NOT use for write operations (insert, update, delete, migrate, schema change) or for projects without the /agent-mcp endpoint; for shell-based one-off calls, use the agent-mcp-cli skill instead.