Agent MCP CLI

Call the agent-mcp read-only tools straight from the shell, without registering an MCP server in the client. The CLI honors the same per-tool config flags, audit log, and best-effort redaction as the HTTP endpoint. Run commands with the project's artisan binary: examples use php artisan, but use the project's form where it differs (for example vendor/bin/sail artisan agent-mcp:call ...).

CLI or MCP server

• Use the CLI for a one-off call, a script, a CI job, or any context where the agent-mcp server is not registered in the client.
• Register the MCP server (the HTTP route or the stdio bridge) when you want persistent, low-latency tool access across many turns. The thesis: do not add an MCP server you only occasionally need; reach for the CLI instead, and register the server when the need is constant.

Workflow

1. Discover: php artisan agent-mcp:tools lists the callable tools (add --all to include tools disabled in config, flagged enabled: false).
2. Inspect inputs: php artisan agent-mcp:schema <tool> prints a tool's input schema.
3. Call: pass a JSON arguments object as a positional argument or on STDIN.
   • php artisan agent-mcp:call db_schema '{"table":"users"}'
   • echo '{"table":"users"}' | php artisan agent-mcp:call db_schema
4. Read the result: the JSON payload goes to stdout (pretty on a terminal, raw when piped, or force raw with --raw); diagnostics go to stderr; the exit code is non-zero on a tool error. Pipe to a processor: php artisan agent-mcp:call db_schema --raw | jq ..

Local and remote