MCP - Connect your AI Agent to PixelFlow

Connect PixelFlow to the AI chat you already use. The chat can set up a site, connect an ad platform, check that tracking works, and answer questions about your events, attribution, and journeys. You approve a change before it is saved. Your chat does the talking. PixelFlow supplies the data and applies what you approved. It never asks you to paste a token, a key, or a password.

This works in Claude, Claude Code, Cursor, ChatGPT, Codex, and Codex CLI. Any other tool that can add a remote MCP server uses the same address: https://api.pixelflow.so/mcp.

Connect

Connect your tool from the dashboard. Both entry points open the same steps.

In PixelFlow, click Connect your AI at the top of the dashboard, or Set up with AI at the start of site setup. After a tool is connected, open AI tools to connect another one or to disconnect one.
Pick your tool and follow the steps on that screen. That screen has the server URL and, where the tool has no / menu, the setup prompt to paste.
When the tool asks you to sign in, use your normal PixelFlow login and click Allow. The tool then shows on AI tools.
Start setup. In Cursor and Claude Code, type / and pick setup_tracking. In Claude, ChatGPT, Codex, and Codex CLI, paste the prompt from the PixelFlow screen and send it.

You stay signed in while you use that tool. If you leave it unused for 30 days, it asks you to sign in again. Disconnecting it on AI tools signs it out immediately.

What you can ask it to do

Name the website by its domain, and say PixelFlow in the message. Picking setup_tracking from the / menu already selects PixelFlow, so that menu item does not need the name again. The chat can only open sites this login can already open in the dashboard.

Set up a site

Try: "Use PixelFlow to set up tracking on shop.example.com."

Create a site, or update the domain and currency on one you already have.
Get the install steps for this site, with your snippet filled in. PixelFlow does not edit the website. A chat that already has the project open, such as Cursor, can place the snippet when you ask it to.
Connect an ad platform, open billing, connect Stripe or Calendly, or open the Visual Tagger. The chat hands you a one-time link. Open it in Chrome, Safari, or Firefox: the sign-in check fails inside the chat's browser. The link lasts 30 minutes. You still sign in to PixelFlow if that browser is not already signed in.
Check the published site the same way site setup does. A preview address is refused. Publish on the site domain first.

Read your numbers

Try: "Using PixelFlow, how did attributed revenue on shop.example.com change over the last 7 days, compared with the 7 days before?"

These match the dashboard. The chat can only read as far back as your plan allows. Trial and Standard: 30 days of Overview and Attribution, and 7 days of Journeys. Growth and Agency: 90 days of each. A longer range is refused. Shorten it, or upgrade. The path inside one journey still looks back 90 days on every plan.

Ask for	What you get
Overview for a date range	Purchases, leads, revenue, delivered and failed, and how many conversion events had an email or phone. Grouped by day or week.
Where revenue came from	Attribution analytics: source, then campaign, ad set, and ad. Sessions and visitors are counted for one calendar day. Revenue and conversion counts cover the whole range.
Who converted, and what they touched	Conversions Journeys. A visitor who only viewed a page is not a row.
Recent events	One page of the Event Logs, newest first. Ask for the next page. There is no page number.
One event's payload	The stored body. Name, email, and phone stay hashed. The IP is shortened unless you ask for the full address.
Blocked events	Counts by reason, event type, or day.
Triggers	The triggers on the site, and how many times each fired in the range.

On a busy site the chat may say the range is too wide, name a shorter range, and say when to ask again. Use that answer.

Track conversions

Try: "Using PixelFlow, what conversions are still missing on shop.example.com?"

After the published site passes the check, the chat can propose the events that are still missing: a purchase, a booking, a form, a signup, or a donation. It shows one list. You approve it once, or strike the lines you do not want. It saves only the lines you approved.

It can add a page, click, or form trigger, and a blocking rule so a refresh does not send the same event twice. It can rename a Pixel, set a test event code, and update or remove a Stripe or Calendly connection.

The methods are the same ones in these guides: a page load, a form, the Visual Tagger, Stripe, and Calendly.

After a trigger is saved, wait about a minute, then test in a private window or after a hard refresh. A tab that was already open can still be using the previous setup. If a test fires nothing, ask the chat to check the selector on the live page.

Prompts

Type / and pick one of these, where your tool has that menu. Otherwise paste the prompt from the PixelFlow connect screen. setup_tracking is the one that starts setup.

Prompt	What it does
`setup_tracking`	Set up tracking. Create or update the site, install, connect an ad platform, verify, then propose the events to track.
`audit_tracking`	Audit a site that is already tracking. Findings come with a fix, and a missed purchase is named before a selector that stopped matching.
`weekly_report`	The last 7 days against the 7 days before: overview, attributed revenue, blocked events, and whether tracking is still healthy.

Limits you will notice

Each connected tool can take about 60 actions a minute. A normal setup uses fewer than that. If you hit the limit, the chat says how long to wait.
The live site check and a selector check share one pass per site per minute.
A preview address is refused. Publish on the site domain, then check again.
A connect link lasts 30 minutes, works once, and has to be opened in Chrome, Safari, or Firefox.
The chat follows the same site cap, ad platform slots, and date range as your plan. A full plan or a canceled plan comes back with a billing link.
There is no way to delete a site or a Pixel from the chat.

Disconnect

Open AI tools and disconnect that tool. Other connected tools keep working.

Ask it about PixelFlow

In the same chat you can ask how PixelFlow works. It can read these help articles and the changelog. For a failure, it should follow the article for that failure.

Was this helpful?