PixelFlow MCP server
2026년 11월 3일 커밋AI agent가 Meta 및 TikTok의 서버 측 전환 추적을 설정하고 기여도 및 이벤트 데이터에 관한 질문에 답변합니다.
다른 이름 PixelFlow-org/mcp, mcp
- 스타
- 3
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 2.0.1
- 마지막 커밋
- 2026년 11월 3일
- 라이선스
- MIT
PixelFlow MCP란?
AI agent가 Meta 및 TikTok의 서버 측 전환 추적을 설정하고 기여도 및 이벤트 데이터에 관한 질문에 답변합니다.
프로젝트 README에서 생성된 요약
PixelFlow MCP server 정보
PixelFlow를 사용하면 AI 채팅 인터페이스를 통해 Meta 및 TikTok의 서버 측 전환 추적을 설정할 수 있습니다. 마케팅 팀과 개발자는 태그 매니저나 수동 코딩 없이 구매, 양식 제출, 예약 전화와 같은 작업에 대한 추적 트리거 설치를 자동화하기 위해 이 서버를 사용합니다. agent가 광고 플랫폼 연결 및 필요한 트리거 생성을 처리하지만, 사이트 설정이나 통합에 대한 모든 변경 사항은 사용자의 승인이 필요합니다.
사용자는 원격 URL을 사용하여 이 서버를 Claude, ChatGPT, Cursor 또는 Claude Code와 같은 클라이언트에 연결합니다. 인증은 API 키나 토큰을 붙여넣는 대신 표준 로그인과 Allow 버튼을 통해 처리됩니다. 연결이 완료되면 agent는 이벤트 데이터, 기여도 세부 정보 및 사이트 상태를 읽어 복잡한 질문에 답변할 수 있습니다. 또한 픽셀 업데이트, Stripe 또는 Calendly와 같은 통합 관리, 트리거 생성 및 삭제 등의 편집을 수행할 수 있지만, 광고 예산, 캠페인 또는 웹사이트의 실제 코드를 변경하는 것은 엄격히 금지됩니다.
활용 사례
- 1전환 추적 설정 자동화AI agent가 PixelFlow 설치 및 구매와 같은 특정 사용자 작업에 대한 트리거 생성을 안내합니다.
- 2기여도 및 매출 분석AI 클라이언트에 지난주에 어떤 특정 캠페인이나 트래픽 소스가 가장 많은 매출을 일으켰는지 보고하도록 요청할 수 있습니다.
- 3추적 불일치 문제 해결광고 플랫폼의 리드 수가 추적 서버와 다르게 표시되는 이유를 agent에게 조사하도록 요청할 수 있습니다.
- 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를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
AI agent가 광고 캠페인이나 예산을 변경할 수 있나요?
아니요, 서버는 광고 계정에 접근할 수 없도록 제한되어 있어 캠페인, 예산 또는 광고를 변경할 수 없습니다.
서버가 웹사이트 코드를 수정하나요?
아니요, 서버는 웹사이트를 수정하지 않습니다. 다만 리포지토리 접근 권한이 있는 코딩 agent라면 제공된 설치 지침을 사용할 수 있습니다.
PixelFlow 인증은 어떻게 하나요?
토큰이나 키를 붙여넣을 필요가 없습니다. 클라이언트를 통해 평소 사용하던 PixelFlow 계정으로 로그인한 뒤 Allow를 클릭하면 됩니다.