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 doctor

beacon mcp doctor validates local Beacon MCP setup before you connect an MCP client. 
beacon mcp doctor
Doctor resolves the effective runtime log path, checks transport settings, reports content retention, samples readable events and archives, and confirms that the expected MCP tools are registered.

​
Checks

Doctor reports:
  • MCP transport
  • Loopback HTTP address and bind check, when --transport http is used
  • Runtime log path and source
  • Runtime log warnings, when present
  • Content retention mode
  • Sampled event count
  • Malformed line count
  • Readable runtime archives
  • Registered MCP tools
If the runtime log does not exist yet, doctor reports that Beacon MCP can still start, but activity answers will be empty until endpoint telemetry writes events.

​
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

Validate stdio MCP setup: 
beacon mcp doctor
Validate loopback HTTP setup: 
beacon mcp doctor --transport http --addr 127.0.0.1:8766
Validate a specific runtime log: 
beacon mcp doctor --log-path /path/to/runtime.jsonl
Validate system-mode paths: 
sudo beacon mcp doctor --system

beacon mcp

Review MCP tools, filters, and command group behavior.

beacon mcp serve

Run the local Beacon MCP server after validation.

Model Context Protocol (MCP)

Understand Beacon MCP and test local client access.

Connect Cursor and Claude Code

Install Beacon MCP in local assistant clients.