MCP & CLI
Enable the Signals API MCP server and signals:api Artisan CLI, and copy connector install instructions.
Overview
MCP & CLI is the admin settings screen for the AI connector surface and the in-process API CLI. Self-hosted installs turn each transport on here before clients can connect.
Where it lives
Route: /admin/settings/mcp-cli (admin.settings.mcp-cli)
Open Admin → Users & Security → MCP & CLI. Requires settings.manage.
Settings
| Group | Keys | Effect |
|---|---|---|
mcp |
enabled, http_enabled, stdio_enabled |
Master switch plus per-transport gates for the MCP server |
mcp |
read_only |
Restricts MCP to reads — write tools disappear from tools/list and execute-endpoint refuses anything but GET/HEAD. See read-only mode |
mcp |
session_unit_budget |
Weighted API units one MCP session may spend before every further tool call returns a normal budget-exhausted result. 0 (default) = unlimited. See session unit budget |
api_cli |
enabled |
Master switch for php artisan signals:api |
When MCP HTTP is enabled, the page shows the install URL (/mcp/api) and copy-paste instructions for Claude, Claude Code, and ChatGPT. Tokens are minted on API Tokens; the token owner needs mcp.access (MCP) or cli.access (mutating CLI calls).
Related
- MCP server — full install, coverage model, and LLM instructions
- API CLI —
signals:apireference and scripting - API Tokens