PixelFlow MCPサーバー
コミット 2026年11月3日AIエージェントがMetaとTikTokのサーバーサイドコンバージョン計測の設定を行い、アトリビューションやイベントデータに関する質問に回答します。
別名 PixelFlow-org/mcp, mcp
- スター
- 3
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 2.0.1
- 最終コミット
- 2026年11月3日
- ライセンス
- MIT
PixelFlow MCPとは
AIエージェントがMetaとTikTokのサーバーサイドコンバージョン計測の設定を行い、アトリビューションやイベントデータに関する質問に回答します。
プロジェクトのREADMEから生成された概要
PixelFlow MCP server について
PixelFlowは、AIチャットインターフェースを通じてMetaとTikTokのサーバーサイドコンバージョン計測の設定を可能にします。マーケティングチームや開発者は、このサーバーを利用することで、タグマネージャーや手動でのコーディングを行うことなく、購入、フォーム送信、予約などのアクションに対するトラッキングトリガーのインストールを自動化できます。エージェントは広告プラットフォームへの接続と必要なトリガーの作成を処理しますが、サイト設定や統合に関する変更を行うにはユーザーの承認が必要です。
ユーザーは、リモートURLを使用して、このサーバーをClaude、ChatGPT、Cursor、またはClaude Codeなどのクライアントに接続できます。認証は、APIキーやトークンを貼り付けるのではなく、標準的なログインと「Allow」ボタンを介して行われます。接続されると、エージェントはイベントデータ、アトリビューションの詳細、サイトのステータスを読み取り、複雑な質問に回答できます。また、ピクセルの更新、StripeやCalendlyなどの統合管理、トリガーの作成や削除などの編集も実行できますが、広告予算、キャンペーン、またはウェブサイト自体のコードへの変更は厳格に回避されます。
できること
- 1コンバージョン計測設定の自動化AIエージェントがPixelFlowのインストールから、購入などの特定のユーザーアクションに対するトリガー作成までをガイドします。
- 2アトリビューションと収益の分析先週、どの特定のキャンペーンやトラフィックソースが最も多くの収益をもたらしたかについて、AIクライアントにレポートを依頼できます。
- 3トラッキングの不一致に関するトラブルシューティング広告プラットフォームのリード数とトラッキングサーバーの数値が異なる理由について、エージェントに調査を依頼できます。
- 4サイトトラッキングの健全性監査PixelFlowスクリプトが正しくインストールされているか、イベントがブロックされていないかを確認するためのステータスレポートをリクエストできます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
PixelFlow MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにPixelFlow MCPをインストール
$ claude mcp add --transport http mcp https://api.pixelflow.so/mcpCursorにPixelFlow MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://api.pixelflow.so/mcp"
}
}
}VS CodeにPixelFlow MCPをインストール
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://api.pixelflow.so/mcp"
}
}
}VS Code CLIにPixelFlow MCPをインストール
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://api.pixelflow.so/mcp"}'CodexにPixelFlow MCPをインストール
$ codex mcp add mcp --url https://api.pixelflow.so/mcpCodex config.tomlにPixelFlow MCPをインストール
~/.codex/config.toml
[mcp_servers.mcp] url = "https://api.pixelflow.so/mcp"
Gemini CLIにPixelFlow MCPをインストール
$ gemini mcp add -s user --transport http mcp https://api.pixelflow.so/mcpGemini settings.jsonにPixelFlow MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://api.pixelflow.so/mcp",
"type": "http"
}
}
}自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能pixelflow-org/mcp is public and reachablegithub.com/pixelflow-org/mcp ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-03github.com/pixelflow-org/mcp ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答HTTPS endpoint answered 401 (sign-in required)合格
README
GitHubで見る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 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.
PixelFlow MCPのよくある質問
PixelFlow MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --transport http mcp https://api.pixelflow.so/mcpを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
PixelFlow MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
AIエージェントが広告キャンペーンや予算を変更することはありますか?
いいえ、このサーバーは広告アカウントへの操作が制限されているため、キャンペーン、予算、広告を変更することはできません。
サーバーがウェブサイトのコードを編集することはありますか?
いいえ、サーバーがウェブサイトを編集することはありません。ただし、リポジトリへのアクセス権を持つコーディングエージェントであれば、提供されたインストール手順を利用することは可能です。
PixelFlowの認証方法を教えてください。
トークンやキーを貼り付ける必要はありません。クライアントから通常のPixelFlowログインを行い、「Allow」をクリックするだけで完了します。