meta-horizon-developer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| META_HORIZON_APP_ID | Yes | The target app ID (maps to --app-id). | |
| META_HORIZON_CSV_DIR | No | Directory for CSV exports (maps to --csv-dir). | |
| META_HORIZON_STATE_DIR | No | Parent directory for default profile, snapshot, and csv directories. Defaults to ./.state/meta-horizon-developer. | ./.state/meta-horizon-developer |
| META_HORIZON_OUTPUT_DIR | Yes | Directory to write snapshots (maps to --snapshot-dir). | |
| META_HORIZON_PROFILE_DIR | No | Directory for the Chromium profile (maps to --profile-dir). | |
| META_HORIZON_LOOKBACK_DAYS | No | Number of days to look back for data collection (maps to --lookback-days). Defaults to 120. | 120 |
| PLAYWRIGHT_CHROMIUM_EXECUTABLE | No | Path to the Chromium executable. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meta_horizon_developer_statusC | Return latest collection health for one application. app_id: target application ID. snapshot_dir: directory holding that application's snapshots. |
| meta_horizon_developer_collectA | Collect allow-listed aggregate GraphQL Queries into a new snapshot. Requires profile_dir because it drives an authenticated browser. Fails immediately with ProfileBusyError when another process already holds that profile. |
| meta_horizon_developer_latest_snapshotB | Return latest snapshot metadata and collection health, not the large payload. |
| meta_horizon_developer_read_operationC | Read one allow-listed aggregate Query from the latest redacted snapshot. |
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 4 tools
The status and latest_snapshot tools both report collection health, creating ambiguity about which to use. collect and read_operation are clearly distinct, but the overlap between the two status-related tools is confusing.
Tool names mix conventions: 'status' and 'latest_snapshot' are noun phrases, while 'collect' and 'read_operation' start with verbs. There is no consistent verb-first or predictable pattern, making it hard to guess the right tool.
With 4 tools, the server is tightly scoped, which is appropriate for a niche developer-oriented MCP. However, the duplicate health functionality between status and latest_snapshot suggests the count could be reduced without losing capability.
The core workflow of collecting snapshots and reading operations is covered, but there is no tool to list snapshots, retrieve a specific non-latest snapshot, or manage the snapshot lifecycle. The overlap between status and latest_snapshot also indicates the surface is not fully refined.