Skip to main content

Command overview

beacon mcp serve starts the local Beacon MCP server over stdio or loopback HTTP JSON-RPC.
Command syntax
The server reads the configured Beacon runtime JSONL log and the approved-memory store next to the endpoint log base directory. It exposes compact activity tools plus read-only approved-memory tools to MCP clients. Use stdio for clients that launch Beacon as a subprocess. Use HTTP only for local loopback testing or local tools that connect to a running server. Registered tools:
  • search_activity
  • summarize_activity
  • get_activity_event
  • list_activity_filters
  • search_memory
  • get_memory
  • get_memory_context

Flags

Examples

Run over stdio for desktop MCP clients:
Run over stdio for desktop MCP clients
Example stdio client configuration:
Run over loopback HTTP JSON-RPC:
Run over loopback HTTP JSON-RPC
Use a specific runtime log:
Use a specific runtime log

HTTP endpoints

Do not bind HTTP transport to a non-loopback interface. Beacon MCP is designed for local activity inspection, not remote administration.

beacon mcp

Review MCP tools, filters, and command group behavior.

beacon mcp doctor

Validate local Beacon MCP setup before connecting a client.

Connect Cursor and Claude Code

Install Beacon MCP in local assistant clients.