Skip to main content

Command Overview

The beacon mcp command group exposes local Beacon endpoint activity to MCP clients so an assistant can search, summarize, and retrieve compact event records from the local runtime.jsonl log.
Command syntax
The server reads the same local runtime log used by the dashboard. It supports stdio for desktop MCP clients and loopback HTTP JSON-RPC for local tools that connect to a running server.

Commands

beacon mcp serve

Run the local Beacon MCP server.

beacon mcp doctor

Validate local Beacon MCP setup and print client configuration.

MCP tools

Beacon exposes these MCP tools: Search and summary tools accept filters such as since, until, limit, q, harness, model, action, severity, category, repository, session, file, command, mcp, approval, decision, policy, review, and wazuh_level.

Flags

beacon mcp only reads local Beacon runtime logs. It does not require a hosted Beacon account, and HTTP transport should remain bound to loopback.

beacon mcp serve

Run the local Beacon MCP server.

beacon mcp doctor

Validate local Beacon MCP setup.

Connect Cursor and Claude Code

Install Beacon MCP in local assistant clients.

Dashboard

Inspect the same local activity log in a browser.

Endpoint event schema

Review the normalized JSONL fields behind MCP activity results.