You'll need the key we emailed you. Pick your tool, replace YOUR_KEY with it, and you're done. Don't have a key yet? Ask for one.
https://statusline.ai/mcp
One command in your terminal, then restart Claude Code. Type /mcp inside a session to confirm the Statusline tools are listed.
claude mcp add --transport http statusline https://statusline.ai/mcp \
--header "Authorization: Bearer YOUR_KEY"
Hermes reads ~/.hermes/config.yaml. Add the server there, put the key in ~/.hermes/.env as STATUSLINE_MCP_KEY, and restart. The tools register as mcp__statusline__*, so any profile or cron job can call them, which is exactly how the end-of-day lap above runs.
mcp_servers:
statusline:
url: "https://statusline.ai/mcp"
headers:
Authorization: "Bearer ${STATUSLINE_MCP_KEY}"
Already running? /reload-mcp picks up the change without a restart. Want Hermes to only read? Everything but ask-ai-tool already is, but you can also list it under tools: exclude:.
Add this to ~/.cursor/mcp.json (or Settings → MCP → Add new server). Cursor lists the tools as soon as the file saves.
{
"mcpServers": {
"statusline": {
"url": "https://statusline.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}
Add this to .vscode/mcp.json in your workspace, then run MCP: List Servers from the command palette and start it.
{
"servers": {
"statusline": {
"type": "http",
"url": "https://statusline.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}
https://statusline.ai/mcp.Authorization with the value Bearer YOUR_KEY.Request headers on custom connectors are still rolling out across Claude plans. If you don't see the field yet, connect through Claude Code or Cursor, or ask us and we'll get you sorted.
MCP is an open protocol. Any client or agent framework that supports remote servers over HTTP works: point it at the URL and send the key as a bearer token. Here's the raw handshake if you're wiring it up yourself.
curl -X POST https://statusline.ai/mcp \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Building an ops agent for your business? This is the layer it should sit on, the same way the Hermes setup above does. Your agent gets classified calls, alerts, and the daily briefing without rebuilding a transcription-and-classification pipeline of its own.