프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

PixelFlow

제작자: PixelFlow-org버전 2.0.1i★ –i클라우드에서 실행
레지스트리 이름so.pixelflow/pixelflow

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: Streamable HTTP
  • 카테고리: 마케팅 및 소셜 미디어

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

  • 기본 점검: 1개 중 1개 통과
  • 제작자의 서버에서 실행돼요. 내가 요청한 내용은 제작자의 서버를 거쳐요.
  • 레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:

  1. Settings → Connectors 열기
  2. Add custom connector 누르기
  3. 아래 주소를 붙여 넣고 Add 누르기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Add2https://…3
https://api.pixelflow.so/mcp

터미널에서 이 명령어를 실행하세요

claude mcp add --transport http pixelflow https://api.pixelflow.so/mcp

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:

  1. 웹에서 ChatGPT 열기 → Settings → Connectors (Apps)
  2. Create 또는 Add 누르기(일부 요금제는 먼저 Advanced에서 Developer mode를 켜야 해요)
  3. 아래 주소를 붙여 넣고 이름을 정한 뒤 저장하기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Create2https://…3
https://api.pixelflow.so/mcp

메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 도메인 pixelflow.so 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    엔드포인트 응답

    아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요

  • … 아직 점검 안 함

    OAuth로 로그인

    아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 2953개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 2953개 중 90%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 2953개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

PixelFlow, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(2.0.1)은 3일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

MCP YouTube Transcript

제작자: jkawamoto

An MCP server retrieving transcripts of YouTube videos

내 컴퓨터에서 실행★ 495MIT9일 전 업데이트
설치

Google Analytics MCP

제작자: surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

내 컴퓨터에서 실행★ 244MIT9일 전 업데이트
설치

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

클라우드에서 실행★ 137MIT9일 전 업데이트
설치

제작자의 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:

  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 Pixel

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기