PixelFlow MCP server
online · 100% uptimeso.pixelflow/pixelflow·v2.0.1·2 starsServer-side conversion tracking for Meta, TikTok, etc. Set up tracking and ask about events.
not scanned yet
2 stars
Reviews
Write oneNobody has reviewed PixelFlow yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
PixelFlow tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How PixelFlow compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 365 ms
- faster than 40% of 30,031 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
Release history: 3 versions in the registry since 2026-10-23, latest 2026-11-03, typically one every 10 days.
Install PixelFlow in Claude Code, Cursor or VS Code
claude mcp add --transport http pixelflow https://api.pixelflow.so/mcp
What the publisher says
From the PixelFlow repository's README, as published. We do not edit it. Read it on GitHub
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
<!-- tools:start --> listsites: List sites. Reads. getsitestatus: Get site status. Reads. getinstallinstructions: Get install instructions. Reads. verifytracking: Verify tracking. Loads the customer's site. getconnectlink: Get connect link. Edits. updatepixel: Update pixel. Edits. updateintegration: Update integration. Edits. disconnectintegration: Disconnect integration. Deletes. createsite: Create site. Edits. updatesite: Update site. Edits. getoverview: Get overview. Reads. getattribution: Get attribution. Reads. getjourneys: Get journeys. Reads. listevents: List events. Reads. geteventpayloads: Get event payloads. Reads. getblockedevents: Get blocked events. Reads. listtriggers: List triggers. Reads. suggesttriggers: Suggest triggers. Reads. checkselector: Check selector. Loads the customer's site. listrecentchanges: List recent changes. Reads. createtrigger: Create trigger. Edits. updatetrigger: Update trigger. Edits. deletetrigger: Delete trigger. Deletes. upsertblockingrule: Save blocking rule. Edits. deleteblockingrule: Delete blocking rule. Deletes. closegetstarted: Close get started. Edits. ensurewebflowecommercetriggers: Ensure Webflow ecommerce triggers. Edits. <!-- tools:end -->
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:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
PixelFlow: common questions
- Is PixelFlow MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the PixelFlow safety report
- How do I install PixelFlow?
- It runs remotely at api.pixelflow.so. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does PixelFlow need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is PixelFlow maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v2.0.1.
- Is PixelFlow up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does PixelFlow compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 365 ms (faster than 40% of 30,031 servers). Full comparison.