In this guide
- The Open Tracked MCP server is free and open source. Every account can create a token under Settings, MCP.
- It runs on your computer and needs Node.js 20 or newer and an MCP app such as Claude Desktop, Claude Code or Cursor.
- It can list containers, check the tracking score, switch power-ups, manage domains and build the Tag Manager files.
The Model Context Protocol (MCP) is an open standard that lets an AI app use tools outside the chat. An MCP server is the small program that offers those tools. The Open Tracked MCP server offers tools for your Open Tracked account, so an assistant can answer "why is my tracking score 60?" from your real data instead of guessing. It is free, open source and included with every account. This page explains what it does, how it works and how to get it. The click-by-click guide is in how to set up the Open Tracked MCP server, and the Tag Manager side is on the GTM MCP server page.
What you need
| Item | Detail |
|---|---|
| Price | Free, included with every Open Tracked account |
| Node.js | Version 20 or newer |
| An Open Tracked token | Create it in Settings, MCP |
| An MCP app | Claude Desktop, Claude Code, Cursor or any app that supports MCP |
| Where it runs | On your own computer |
The code is on GitHub. Create a free account at app.opentracked.io if you do not have one.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
How it works
The server is a bridge. Your AI app starts it on your computer and asks what it can do. When you ask about your tracking, the assistant calls one of its tools. The server asks Open Tracked with your token, and the answer comes back to the chat. Nothing passes through a third party.
The tools
| Tool | What it does |
|---|---|
open_tracked_containers | Lists your containers, or shows one with its domains |
open_tracked_domains | Lists, adds or removes the subdomains of a container |
open_tracked_tracking_score | Gives the container's score from 0 to 100 and the checks behind it: server running, own subdomain, CDN, Custom Loader, Cookie Keeper, events arriving |
open_tracked_power_ups | Shows which power-ups are on, and switches one on or off |
open_tracked_gtm_pack | Builds the web and server Google Tag Manager containers for a shop, the same files the Setup Wizard gives |
open_tracked_install_gtm_pack | Builds them and puts them into Tag Manager as a new workspace in your web container and one in your server container. Nothing is published. Needs Google credentials |
gtm_* (20 tools) | The Tag Manager API: accounts, containers, workspaces, tags, triggers, variables, templates, clients, transformations, versions and publishing. Needs Google credentials |
Connected in minutes
Add your domain, install the pixel, connect your ad platforms and watch the first events land.
Questions to try
- "Which of my containers is close to its monthly limit?"
- "Why is the tracking score of my main container 60, and what do I switch on to fix it?"
- "Turn on Cookie Keeper for container 12 and tell me what else it needs."
- "Add the subdomain data.myshop.com to container 12."
Benefits
Quicker checks
Ask for the score, the power-ups or the domains instead of opening four pages.
Several containers, one question
Compare plans, usage and settings across all your containers at once.
Setup in one request
The install tool creates the tags, variables, triggers, templates and clients in a new workspace, so you only look and publish.
Safe by design
The token reaches only your own containers. Your container's API key and billing details are never passed to the assistant, and you can remove the token at any time.
How to get started
Get the server
Clone the repository from GitHub and build it.
Create a token
In Open Tracked, Settings, MCP.
Add it to your AI app
With the token as an environment variable.
Restart and check
Ask the assistant to list your containers.
Connect Tag Manager if you want that side
With a Google credential. See the GTM MCP server.
The step-by-step guide with the exact configuration is in how to set up the Open Tracked MCP server.
Good habits
- Start with read-only questions.
- Ask the assistant to say what it changed.
- Review any workspace before you publish.
- Keep your token secret and remove it when you no longer need it.
For safe working practices with Tag Manager read AI controls for Google Tag Manager, and for example prompts see AI assistant prompts for tracking.
Orders from your store, back to the ad that earned them
Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.
Frequently asked questions
What is the Open Tracked MCP server?
A free, open-source program that lets an AI assistant work with your Open Tracked containers, domains, power-ups and tracking score, and with Google Tag Manager.
Is it free?
Yes. It is included with every Open Tracked account.
Where does it run?
On your own computer. It talks to Open Tracked with your token.
Can it publish my Tag Manager container?
The Tag Manager tools can create versions and publish when you ask. The install tool never publishes. Keep publishing for yourself.
Which AI apps work with it?
Claude Desktop, Claude Code, Cursor and any app that supports MCP.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...

