beacon-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEACON_ORG | No | Default organisation ID; tools can override per-call via the org argument | default |
| BEACON_PROXY | No | Optional HTTP proxy for requests to BEACON_BASE_URL. Accepts http://, https://, socks5://. | |
| MCP_HTTP_HOST | No | HTTP transport host (only with --http) | 127.0.0.1 |
| MCP_HTTP_PORT | No | HTTP transport port (only with --http) | 8765 |
| BEACON_API_KEY | No | Optional bearer token (sent as Authorization: Bearer …) | |
| BEACON_BASE_URL | No | Beacon REST API base URL | http://127.0.0.1:8080 |
| BEACON_TIMEOUT_MS | No | Per-request timeout in milliseconds | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_organizationsA | List all beacon organizations (tenants) available via the configured beacon API. Call this first if you don't know which org to query. |
| health_checkA | Check whether the beacon API is reachable and the (optional) org is healthy. |
| get_configA | Read the public beacon configuration for an org (min session event count, model pricing). |
| get_dashboardA | Fetch the beacon dashboard payload (or a single sub-section) for the given date range. Returns metrics, activity, traffic, prompt/distribution breakdowns, and the top projects/sessions. |
| query_project_summaryA | Daily rollup per project: event/request counts and token usage. Use for 'which project uses the most tokens this week' questions. |
| query_language_summaryA | Daily rollup per programming language (from session language detection). Use to identify which languages AI assistants are most often working in. |
| query_prompt_style_summaryA | Daily rollup per prompt style (rule-classified). Useful for understanding how users phrase their requests. |
| query_employee_hourly_summaryA | Per-user, per-hour usage broken down by tool and model. Use to find power users, peak hours, and per-model consumption. |
| query_session_summaryA | Per-session rollup: which sessions used the most tokens, their models, timestamps, etc. Use to find the heaviest sessions before drilling in with get_session_events. |
| query_eventsA | Raw event query with date range, project/model/status/user filters and pagination. Use for inspecting individual events (errors, specific users, model behaviour, prompt previews). By default returns up to 100 rows; pass |
| get_session_eventsA | Fetch the full event chain for a single session (compact prompt previews, token usage, errors, model). Use after query_session_summary to drill into the heaviest sessions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| orgs | |
| config | |
| dashboard |
TDQS
Scored across 11 tools
Each tool targets a distinct aspect of the beacon API: configuration, dashboards, session details, health, organizations, and various summaries (employee, events, language, project, prompt style, sessions). There is no overlap in purpose.
Most tools follow a consistent verb_prefix pattern: get_ for specific fetches, list_ for listings, query_ for summaries. However, health_check deviates from the pattern, and get_session_events vs query_session_summary have similar domains with different prefixes.
11 tools is well-scoped for an analytics server. It covers essential operations (config, health, org listing, session detail, and multiple summary queries) without being excessive.
The tool set appears complete for read-only analytics: it covers configuration, health, organization selection, raw events with pagination, and various rollups. Missing create/update/delete tools, but those are likely out of scope for an analytics API.