PixelFlow

so.pixelflow由 pixelflow.so 發布官方發布者v2.0.1更新於 Nov 3, 2026

面向 Meta、TikTok 等的伺服器端轉化跟蹤。設定跟蹤並查詢事件。

AI 翻譯由 AI 模型根據下方的原文描述翻譯，可能有誤。

原文描述

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

已驗證Streamable HTTP可網頁執行資料與分析商業與電商

概覽

PixelFlow 的託管 MCP 服務（api.pixelflow.so），由 pixelflow.so 發布；需要 OAuth 登入；Streamable HTTP。

暫無 AI 概覽：以下資訊來自註冊中心條目和服務本身。

發布者
pixelflow.so
端點
api.pixelflow.so
最近檢查

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 PixelFlow，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/so.pixelflow%2Fpixelflow/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

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

README

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:

  1. 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.
  2. 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

ReadsEvents, attribution, journeys, and site status. Reads do not need approval.
EditsCreating, 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 touchesThe customer's ad account. The server does not change campaigns, budgets, or ads.
Never touchesThe 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 touchesTokens, keys, and passwords. They are not returned and must not be typed into the chat.
Never touchesA visitor's raw email, phone, or name. Hashed values stay hashed. IP stays masked unless the customer asks for the full value.
Never touchesDeleting a Site or a Pixel. Those tools do not exist.
ToolWhat it doesAccess
list_sitesList 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_valuesList 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_statusGet 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_instructionsGet 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_trackingCheck 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_linkCreate a one-time link to the PixelFlow dashboard page for a step that needs a browser sign-in or a secret.Edits
update_pixelChange the label or the test event code of a connected ad platform pixel.Edits
update_integrationChange the settings of an integration connected to a site, such as Stripe or Calendly.Edits
disconnect_integrationDisconnect an integration such as Stripe or Calendly from a site and return which one was removed.Deletes
create_siteAdd a new website to a PixelFlow workspace and return the saved site with its site_id.Edits
update_siteChange settings on a site (domain, platform, currency, ecommerce flags, or Get Started checklist items) and return the saved site.Edits
get_overviewGet 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_attributionGet 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_journeysGet visitor journeys on one site, one row per visitor with an event in the date range.Reads
list_eventsList the tracked events on one site as rows, up to 100 per call.Reads
get_event_payloadsGet the payload (request body) PixelFlow sent to each ad platform for up to 25 events by id.Reads
get_blocked_eventsList 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_triggersList every conversion trigger on one site, including integrations such as Stripe.Reads
suggest_triggersSuggest the conversion triggers a site still needs: which events are tracked today, and one proposal per gap.Reads
create_triggerCreate 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_triggerChange an existing trigger of type url, click, or submit and return the saved trigger.Edits
delete_triggerDelete a trigger of type url, click, or submit and return the id and type of the removed trigger.Deletes
save_blocking_ruleSave the blocking rule for one event on a site, such as Purchase, or for all events (AllEvents).Edits
delete_blocking_ruleDelete the blocking rule for one event on a site, such as Purchase, or the AllEvents rule.Deletes
close_get_startedCheck 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:

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

Start:

  1. Open a new chat in Claude.
  2. 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:

  1. Open a terminal. Do not run this inside a Claude Code chat.
  2. Run:
claude mcp add --transport http --scope user pixelflow https://api.pixelflow.so/mcp
  1. Start Claude Code, run /mcp, and choose PixelFlow.
  2. Choose Authenticate. Sign in with your normal PixelFlow login in the browser that opens, then click Allow.

Start:

  1. 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.
  2. 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:

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

Start:

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

Codex

Connect:

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

Start:

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

Cursor

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

Connect:

  1. In Cursor, click the gear icon at the top right, then Customize.
  2. Click MCPs, then New MCP Server, then User.
  3. 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"}
  1. 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:

  1. 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.
  2. 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:

  1. Open a terminal.
  2. Run:
codex mcp add pixelflow --url https://api.pixelflow.so/mcp
  1. Sign in with your normal PixelFlow login in the browser that opens, then click Allow.

Start:

  1. Open a new Codex CLI chat.
  2. 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:

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

Start:

  1. Open your project chat. PixelFlow now appears under your chat connectors.
  2. 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:

  1. 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.
  2. Name it PixelFlow and use https://api.pixelflow.so/mcp. Streamable HTTP is the transport.
  3. When the client opens a PixelFlow sign-in, use your normal PixelFlow login, then click Allow.

Start:

  1. 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 PixelFlow dashboard, where you can connect another tool or disconnect this one. You stay signed in while you use it; after 30 days unused it asks you to sign in again. Prefer guided steps? Click AI Tools in the dashboard, or Set up with AI at the start of site setup.

Prompts

setup_tracking: Create or update a site, return the snippet or the plugin steps, connect an ad platform, verify, and set up the conversions to track, including a duplicate pixel.

audit_tracking: Health check of a running site. Findings are ordered by revenue impact, and each one includes its fix.

weekly_report: Last 7 days against the 7 days before: overview numbers, attributed revenue, blocked events, and whether tracking is still healthy.

The pasteable setup prompt is on https://pixelflow.so/features/mcp.

來源：README.md，提交 8992c5e

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

3
  1. v2.0.1最新Nov 3, 2026
  2. v1.0.1Oct 23, 2026
  3. v1.0.0Oct 22, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分