AI assistants · MCP
Your tracking, one question away.
Pixelary’s MCP server lets your AI assistant read your stats and event log, audit your setup and, if you allow it, change triggers after you see a preview. It works on every plan: on a free site, stats and the log stay empty, while audits and triggers work.
What to ask
Plain questions,answers from your own data.
-
“Audit the tracking on brightside.studio and tell me what to fix first.”
Checks events, the script, tokens, match quality, the consent banner and missing values.
-
“Which events failed in the last day, and what did the platform say?”
Reads the event log with each platform’s answer.
-
“How many purchases did we send to Meta this week?”
Reads the same numbers as the Overview, for 1, 7, 30 or 90 days.
-
“Is any pixel still in test mode?”
Lists pixels with their mode and whether server-side is set up. Never a token.
-
“Add a Lead trigger for the contact form on /contact.”
Shows a preview of the change. Nothing is saved until you agree.
-
“Switch off the Newsletter trigger.”
Same two steps, and it reaches your site without a republish.
Control
It cannot change anythingyou did not agree to.
-
Read only by default
A new token can only read. Editing triggers is a separate choice when you create it, and it cannot be changed later.
-
Preview, then change
A write first returns a preview and changes nothing. The second call needs a one-time ID that lasts 10 minutes and fits only that change.
-
Your role, your sites
A token acts as you: Owner, Editor or Viewer on each site. Lose access to a site, and the token loses it at the next call.
-
Log text is data
Event names and page paths come from visitors. Pixelary marks them as untrusted and the tools tell assistants not to follow them.
The tools
-
list_sitesYour sites and your role on each -
site_overviewEvents, deliveries, failures and recovered conversions -
recent_eventsThe event log, filtered by status and name -
audit_trackingWhat is wrong on a site and what to fix -
list_pixelsPlatform, ID, mode and server-side state -
list_triggersWhat each trigger fires on and sends -
create_triggerAdds a trigger, after a preview -
update_triggerChanges a trigger, after a preview -
set_trigger_enabledSwitches a trigger, after a preview
What it cannot do
- Create a site, connect a pixel or install the script. You do that in the dashboard.
- See access tokens, billing, the team or data exports, or change domains or consent settings.
- Delete anything.
- Connect through OAuth. Your client must let you set a request header, so most Claude and ChatGPT app connectors cannot use it yet.
What your assistant reads goes to its provider, under your agreement with them. The event log holds no contact details or IP addresses. Security details
Stop losing conversions you already paid for.
Free browser pixel today. Try server-side free for 14 days when you are ready.