Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.asymptotelabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
beacon mcp serve

beacon mcp serve starts the local Beacon MCP server over stdio or loopback HTTP JSON-RPC. 
beacon mcp serve
The server reads the configured Beacon runtime JSONL log and exposes compact activity 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.

​
Flags

FlagDescription
--userUse per-user endpoint paths. Enabled by default
--systemUse system endpoint paths
--log-path PATHRuntime JSONL log path
--transport stdio|httpMCP transport. Defaults to stdio
--addr ADDRLoopback HTTP JSON-RPC listen address for --transport http. Defaults to 127.0.0.1:8766

​
Examples

Run over stdio for desktop MCP clients: 
beacon mcp serve --transport stdio
Example stdio client configuration: 
{
  "mcpServers": {
    "beacon": {
      "command": "beacon",
      "args": ["mcp", "serve", "--transport", "stdio"]
    }
  }
}
Run over loopback HTTP JSON-RPC: 
beacon mcp serve --transport http --addr 127.0.0.1:8766
Use a specific runtime log: 
beacon mcp serve --log-path /path/to/runtime.jsonl

​
HTTP endpoints

PathDescription
/mcpMCP JSON-RPC endpoint
/healthLocal health check endpoint
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.