PixelFlow

Name: PixelFlow
Author: PixelFlow-org

by PixelFlow-orgversion 2.0.1i★ –iRuns in the cloud

Registry nameso.pixelflow/pixelflow

Install

Overview

Description from the maker (original English)

Server-side conversion tracking for Meta, TikTok, etc. Set up tracking and ask about events.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiVery new★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://api.pixelflow.so/mcp

Run this in your terminal

claude mcp add --transport http pixelflow https://api.pixelflow.so/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pixelflow": {
      "url": "https://api.pixelflow.so/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pixelflow": {
      "type": "http",
      "url": "https://api.pixelflow.so/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://api.pixelflow.so/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain pixelflow.so (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 400 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Marketing & social mediai

More stars than 0% of the other 3696 servers in this category
Published to the registry more recently than 81% of the other 3696 servers in this category
Basic checks equal to or better than 100% of the other 3696 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is PixelFlow safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.1) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

MCP YouTube Transcript

An MCP server retrieving transcripts of YouTube videos

by jkawamotoGrowing★ 495Updated 12 days ago

Runs on your computer

Install

Google Analytics MCP

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

by surendranbGrowing↓ 1.1K/wk★ 244Updated 12 days ago

Runs on your computer

Install

BibiGPT YouTube Video Summarizer

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

by JimmyLvGrowing★ 137Updated 13 days ago

Runs in the cloud✓ bibigpt.co

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

PixelFlow MCP Server

PixelFlow is server-side conversion tracking for Meta and TikTok. No tag manager, and no developer needed.

The MCP server lets your AI agent do two things from the chat:

Set up conversion tracking. The agent walks you through the install, connects Meta or TikTok, and creates the triggers for the actions you want to track, such as a form submission, a booked call, or a purchase. You approve the changes.
Answer questions about your tracking and your data. PixelFlow returns the events themselves, so the agent can answer what you ask and build the report in the chat. What was attributed revenue last week? Which campaigns drove purchases? Why is Meta showing more leads than PixelFlow?

The server URL is https://api.pixelflow.so/mcp.

The client opens the PixelFlow login and the customer clicks Allow. No token is pasted.

Reads, edits, and never touches


Reads	Events, attribution, journeys, and site status. Reads do not need approval.
Edits	Creating, editing, or deleting a trigger, a blocking rule, a site field, a pixel label, or an integration. Show the change and wait for one approval.
Never touches	The customer's ad account. The server does not change campaigns, budgets, or ads.
Never touches	The customer's website. The server does not edit it. A coding agent that already has the repo may place the snippet the install tool returned.
Never touches	Tokens, keys, and passwords. They are not returned and must not be typed into the chat.
Never touches	A visitor's raw email, phone, or name. Hashed values stay hashed. IP stays masked unless the customer asks for the full value.
Never touches	Deleting a Site or a Pixel. Those tools do not exist.

Tool	What it does	Access
`list_sites`	List the websites the signed-in user can access in PixelFlow: each site's site_id, domain, platform, currency, whether the user can edit it, and the workspace it belongs to with the user's role there.	Reads
`list_supported_values`	List the names PixelFlow supports and other tools accept: the platforms a site can run on, the ad platforms events can be sent to, the integrations that report conversions, the supported events, and the traffic sources events are attributed to.	Reads
`get_site_status`	Get the setup and health state of one site: its settings (domain, platform, currency, ecommerce flags), whether the PixelFlow script or plugin is installed, connected pixels and integrations, blocking rules, consent mode, the last event received of each type, which Get Started checklist items are done, and the plan, limits, and usage of its workspace.	Reads
`get_install_instructions`	Get step-by-step instructions the user follows on their website or in their ad platform's ads manager, for one task: installing PixelFlow, adding UTM parameters to ad links, removing an ad platform's own pixel code (such as the Facebook pixel) that was added before PixelFlow and would count events twice, or removing PixelFlow.	Reads
`verify_tracking`	Check that tracking works on one site by loading one of its pages in a headless browser and reading the events received since checked_from.	Loads the customer's site
`get_connect_link`	Create a one-time link to the PixelFlow dashboard page for a step that needs a browser sign-in or a secret.	Edits
`update_pixel`	Change the label or the test event code of a connected ad platform pixel.	Edits
`update_integration`	Change the settings of an integration connected to a site, such as Stripe or Calendly.	Edits
`disconnect_integration`	Disconnect an integration such as Stripe or Calendly from a site and return which one was removed.	Deletes
`create_site`	Add a new website to a PixelFlow workspace and return the saved site with its site_id.	Edits
`update_site`	Change settings on a site (domain, platform, currency, ecommerce flags, or Get Started checklist items) and return the saved site.	Edits
`get_overview`	Get tracking totals for one site over a date range: the count of each event, such as Purchase or Lead, revenue, events delivered and failed per pixel, events blocked by consent or bot detection, event counts per day or week, and, for the newest 500 conversions in the range, how many carried a hashed email or phone.	Reads
`get_attribution`	Get revenue and conversions for one site over a date range, broken down by traffic source, campaign, ad set, or ad, using PixelFlow's website attribution (the UTM tags and referrer of the converting visit).	Reads
`get_journeys`	Get visitor journeys on one site, one row per visitor with an event in the date range.	Reads
`list_events`	List the tracked events on one site as rows, up to 100 per call.	Reads
`get_event_payloads`	Get the payload (request body) PixelFlow sent to each ad platform for up to 25 events by id.	Reads
`get_blocked_events`	List the events PixelFlow did not send to ad platforms on one site because of consent or bot detection, up to 100 per call.	Reads
`list_triggers`	List every conversion trigger on one site, including integrations such as Stripe.	Reads
`suggest_triggers`	Suggest the conversion triggers a site still needs: which events are tracked today, and one proposal per gap.	Reads
`create_trigger`	Create a trigger that sends an event to the site's ad platforms when a visitor submits a form, clicks an element, or loads a page, and return the saved trigger with its trigger_id.	Edits
`update_trigger`	Change an existing trigger of type url, click, or submit and return the saved trigger.	Edits
`delete_trigger`	Delete a trigger of type url, click, or submit and return the id and type of the removed trigger.	Deletes
`save_blocking_rule`	Save the blocking rule for one event on a site, such as Purchase, or for all events (AllEvents).	Edits
`delete_blocking_rule`	Delete the blocking rule for one event on a site, such as Purchase, or the AllEvents rule.	Deletes
`close_get_started`	Check the site's Get Started checklist and mark as done the items PixelFlow can confirm from its data.	Edits

The full description, hints, arguments, and result fields of every tool are in TOOLS.md, generated from the server.

Claude

Guide: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

Connect:

In Claude, click Customize, then Connectors, then Add, then Add custom connector.
Type PixelFlow in the Name field.
Copy and paste https://api.pixelflow.so/mcp into the MCP server URL field.
Click Continue, then Add.
Click Connect, then Continue Connecting. Sign in with your normal PixelFlow login if asked, then click Allow.

Start:

Open a new chat in Claude.
Copy and paste the setup prompt from https://pixelflow.so/features/mcp into the chat, then send it. Claude has no / menu for prompts, so the pasted prompt is what starts setup.

Custom connectors work on every Claude plan (free plans are limited to one). On Team and Enterprise plans an owner adds the connector first, under Organization settings, then Connectors.

Claude Code

Guide: https://code.claude.com/docs/en/mcp

Connect:

Open a terminal. Do not run this inside a Claude Code chat.
Run:

claude mcp add --transport http --scope user pixelflow https://api.pixelflow.so/mcp

Start Claude Code, run /mcp, and choose PixelFlow.
Choose Authenticate. Sign in with your normal PixelFlow login in the browser that opens, then click Allow.

Start:

In Claude Code, type / and pick setup_tracking, then send it. That menu item already selects PixelFlow, so you do not need to name it.
If setup_tracking is not in the menu, paste the setup prompt from https://pixelflow.so/features/mcp into the chat.

ChatGPT

Guide: https://developers.openai.com/api/docs/mcp

Connect:

In ChatGPT, click Plugins in the left sidebar, then Add, then Add custom MCP server.
Type PixelFlow in the Name field.
Copy and paste https://api.pixelflow.so/mcp into the Connection, Server URL field.
Tick I understand and want to continue, then click Create as a plugin.
Click Continue to PixelFlow. Sign in with your normal PixelFlow login if asked, then click Allow.
In Plugins, search for PixelFlow and open it. Click the Manage icon, then the Permission row, and select Allow all tools.

Start:

Open a new chat in ChatGPT.
Paste the setup prompt from https://pixelflow.so/features/mcp into the chat, then send it.

Codex

Connect:

Open https://chatgpt.com/plugins, then click Add, then Add custom MCP server.
Type PixelFlow in the Name field.
Copy and paste https://api.pixelflow.so/mcp into the Connection, Server URL field.
Tick I understand and want to continue, then click Create as a plugin.
Click Continue to PixelFlow. Sign in with your normal PixelFlow login if asked, then click Allow.
In Plugins, search for PixelFlow and open it. Click the Manage icon, then the Permission row, and select Allow all tools.

Start:

Open a new chat in Codex.
Paste the setup prompt from https://pixelflow.so/features/mcp into the chat, then send it.

Cursor

Guide: https://cursor.com/docs/mcp

Connect:

In Cursor, click the gear icon at the top right, then Customize.
Click MCPs, then New MCP Server, then User.
If mcp.json already has a server, add a comma after it. Then paste the block below inside mcpServers and save the file.

"pixelflow": {

"url": "https://api.pixelflow.so/mcp" }

Go back to MCPs and click Authenticate next to PixelFlow. Sign in with your normal PixelFlow login in the browser that opens, then click Allow. If Authenticate is not listed, reload Cursor.

Start:

Open a new agent chat, type / and pick setup_tracking, then send the message. That menu item already selects PixelFlow, so you do not need to name it.
If setup_tracking is still missing from the menu, paste the setup prompt from https://pixelflow.so/features/mcp into the chat and send it.

Codex CLI

Connect:

Open a terminal.
Run:

codex mcp add pixelflow --url https://api.pixelflow.so/mcp

Start:

Open a new Codex CLI chat.
Paste the setup prompt from https://pixelflow.so/features/mcp into the chat, then send it.

Lovable

Guide: https://docs.lovable.dev/integrations/custom-mcp

Connect:

In Lovable, open Connectors, click the + button at the top right of the catalog, then MCP server.
Name the server PixelFlow and paste https://api.pixelflow.so/mcp as the Server URL.
Leave authentication on OAuth and click Add & authorize, then approve access and pick the workspace to connect.

Start:

Open your project chat. PixelFlow now appears under your chat connectors.
Paste the setup prompt from https://pixelflow.so/features/mcp into the chat, then send it.

Chat connectors are personal to you and are not part of your published app. If MCP server is greyed out, a workspace admin has turned custom servers off.

Other MCP clients

Connect:

Add a remote MCP server in your client. Most ask for a name and a URL. Any tool that can add a remote MCP server uses the same address.
Name it PixelFlow and use https://api.pixelflow.so/mcp. Streamable HTTP is the transport.
When the client opens a PixelFlow sign-in, use your normal PixelFlow login, then click Allow.

Start:

Open a new chat and paste the setup prompt from https://pixelflow.so/features/mcp, then send it.

Works with Gemini CLI, VS Code, Windsurf, Zed and anything else that speaks MCP over HTTP.

PixelFlow never asks you to paste a token, a key or a password: you sign in with your normal login and click Allow. Once connected, the tool shows under AI tools in your Pixel

Only the beginning is shown; read the rest in the repo

PixelFlow

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Marketing & social mediai

Common questions

Alternatives

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README from the maker

PixelFlow MCP Server

Reads, edits, and never touches

Claude

Claude Code

ChatGPT

Codex

Cursor

Codex CLI

Lovable

Other MCP clients