Open Tracked MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | No | Google OAuth client ID. | |
| OPEN_TRACKED_URL | No | Base URL of the Open Tracked app. | https://app.opentracked.io |
| GOOGLE_PRIVATE_KEY | No | Google service account private key. | |
| OPEN_TRACKED_TOKEN | Yes | Token created in Open Tracked under Settings, MCP. It is shown once. | |
| GOOGLE_ACCESS_TOKEN | No | Short-lived Google access token, for trying it out. | |
| GOOGLE_CLIENT_EMAIL | No | Google service account client email. | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret. | |
| GOOGLE_REFRESH_TOKEN | No | Google OAuth refresh token. | |
| GOOGLE_SERVICE_ACCOUNT_KEY | No | Google service account key JSON. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_tracked_containersB | Your Open Tracked containers: 'list' them all, or 'get' one with its domains. |
| open_tracked_domainsB | Subdomains of a container: 'list', 'add' (the response says which CNAME records to create), or 'remove'. A domain can belong to one container only. |
| open_tracked_tracking_scoreB | The container's tracking score (0 to 100) and the checks behind it: server running, own subdomain, CDN, Custom Loader, Cookie Keeper, events arriving. |
| open_tracked_power_upsB | Power-Ups of a container: 'list' which are on, or 'toggle' one (key such as geo_headers (visitor location), user_agent_info (device info), user_id, custom_loader, cookie_keeper). |
| open_tracked_gtm_packA | Build the two Google Tag Manager containers (web and server) for a shop, the same ones the Setup wizard gives. Returns a summary. With outputDir (an absolute folder) the two JSON files are written there, ready for Admin > Import Container. |
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 5 tools
Each tool targets a distinct resource or operation: containers, domains, tracking score, power-ups, and the GTM pack builder. The only mild overlap is that gtm_pack builds containers while containers lists/gets them, but the descriptions make the build action clearly separate.
All five tools use the same open_tracked_ prefix followed by a snake_case resource name. Although they are resource-oriented rather than verb_noun, the convention is applied consistently across the entire set.
Five tools is well-scoped for this server: each tool maps to a distinct area of container management, subdomains, power-ups, tracking score, and initial GTM setup. Nothing feels padded or obviously missing from a count perspective.
The surface covers the main lifecycle operations: list/get containers, create web/server containers via gtm_pack, manage subdomains, toggle power-ups, and read tracking scores. Minor gaps remain, such as deleting containers or editing broader container settings, but agents can work around them.