PixelFlow
概要
作者による説明(英語の原文)
Server-side conversion tracking for Meta, TikTok, etc. Set up tracking and ask about events.
PopNx MCPの3つの柱
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
- 利用者の声iレビューはまだありませんレビューは今後のステップで、アカウント機能と一緒に始まります
- 私たちの基本チェックi3項目中3項目に合格公開情報からチェック。コードはまだスキャンしていません
- 利用状況iとても新しい★ –
できること
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
- 接続方法: クラウドで動く
- トランスポート: Streamable HTTP
- カテゴリ: マーケティング・SNS
インストール
使っているAIアプリを選んで、設定をコピーしてください。
インストールの前に
- 基本チェック:3項目中3項目に合格
- 作者のサーバーで動きます。あなたが頼んだ内容は、作者のサーバーを通ります。
- レジストリには、入力が必要なキーは載っていません。
必要なもの
- クラウドで動くインストール不要。インターネット経由でつながります
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
- Settings → Connectors を開く
- Add custom connector を押す
- 下のアドレスを貼り付けて Add を押す
- サインインを求められたら、作者のサービスにサインインする
https://api.pixelflow.so/mcpターミナルでこれを実行します
claude mcp add --transport http pixelflow https://api.pixelflow.so/mcpまたは、設定を自分でコピーする
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"pixelflow": {
"url": "https://api.pixelflow.so/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
または、設定を自分でコピーする
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"pixelflow": {
"type": "http",
"url": "https://api.pixelflow.so/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
- ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
- Create または Add を押す(プランによっては、先に Advanced で Developer mode をオンにする必要があります)
- 下のアドレスを貼り付け、名前を付けて保存する
- サインインを求められたら、作者のサービスにサインインする
https://api.pixelflow.so/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
できること
このサーバーは、ツール一覧を表示する前にサインインを求めます。
基本チェックi
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック
- ✓ 合格
作者とリポジトリが一致
レジストリ名はドメイン pixelflow.so で確認済みです(レジストリがドメインの所有を確認しています)
- … 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
- … 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
- ✓ 合格
エンドポイントが応答する
400ミリ秒で応答(HTTP 401)
- ✓ 合格
OAuthでサインイン
OAuthでのサインインに対応しているため、AIアプリがログイン画面へ案内してくれます
- … 未チェック
ツールの説明に隠れた指示がない
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
マーケティング・SNSのほかのサーバーとの比較i
- このカテゴリのほかの3610件のうち0%よりスターが多い
- このカテゴリのほかの3610件のうち84%より最近レジストリに公開
- 基本チェックの結果が、このカテゴリのほかの3610件のうち100%と同じかそれ以上
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
よくある質問
PixelFlowは安全ですか?
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
どんなキーやコードが必要ですか?
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
パソコンで動きますか、それともクラウドですか?
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
今もメンテナンスされていますか?
GitHubリポジトリの最終更新は–、最新バージョン(2.0.1)がレジストリに届いたのは5 日前です。
どのアプリで使えますか?
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
代わりに使えるものは?
同じカテゴリには:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
代わりの候補
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Google Analytics MCP
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
作者のREADME
READMEを開く
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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
- Sign in with your normal PixelFlow login in the browser that opens, then click Allow.
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
冒頭だけを表示しています。続きはリポジトリで読めます