Northbeam MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NORTHBEAM_BRAND | Yes | Your Northbeam brand name | |
| NORTHBEAM_API_KEY | Yes | Your Northbeam API key |
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 |
|---|---|
| get_metricD | – |
| list_metricsD | – |
| list_dimensionsD | – |
| get_channel_performanceD | – |
| get_cohort_analysisD | – |
| get_attributionD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct action: listing vs getting metrics, listing dimensions, and three analysis types (channel performance, cohort, attribution). The purposes are clearly separated by resource type and analysis focus.
All tools follow a consistent verb_noun pattern: list_ for enumeration and get_ for single items or report-style analyses. The naming is predictable and easy to generalize.
Six tools is well-scoped for an analytics server, covering exploration (metrics, dimensions) and core analytical operations without being either sparse or overwhelming.
The set covers metric listing/retrieval, dimension listing, and key analytical views. A minor gap is the absence of a way to list specific channels or cohorts directly, but the existing tools likely cover these indirectly via parameters.