Back to landing
SupportTry Beacon
MCP Guide

Connect Beacon to external AI clients over MCP.

Beacon exposes an MCP transport route so external agents can delegate the research task into Beacon's workflow and memory system.

Search docs, support, and public pages
search
Transport

Current MCP surface

Transport route:
  /api/mcp/[...transport]

Current intent:
  let external agents trigger Beacon research
  keep retrieval and memory inside Beacon
  return run metadata instead of forcing all work into the client
Authentication

How clients authenticate

MCP requests can authenticate with a Bearer token. Beacon validates the token against BEACON_MCP_TOKEN, or falls back to BEACON_SESSION_TOKEN if no dedicated MCP token is configured.

Operational Notes

What to expect today

Best for agent workflows

Use MCP when Claude Desktop, Cursor, or another client should ask Beacon to own the research loop.

Not a full public platform yet

Beacon's MCP surface is usable, but the broader packaging and reference docs are still being hardened.