Pixelixe MCP Connectors
Choose your setup guide

MCP endpoint OAuth and Bearer Platform-specific guides

Start here

Pixelixe exposes a single MCP endpoint, but the setup flow changes a lot from one client to another. These guides are split by platform on purpose, because ChatGPT, Claude, n8n, Make, and Zapier do not expose the same MCP UI, auth options, or rollout level.

Pixelixe MCP endpoint:
https://studio.pixelixe.com/api/mcp/v1

Authentication: there are 2 supported options. Use OAuth when the platform offers a Pixelixe sign-in flow. Otherwise, use your own Pixelixe API key as a secure Bearer credential inside the connector setup. Never paste the secret inside the prompt itself or inside a tool argument.

Choose your platform

Connect Pixelixe to ChatGPT

Use this guide if you want Pixelixe inside ChatGPT apps or custom MCP integrations. It explains the plan caveats around Developer Mode and full MCP support.

Open ChatGPT guide

Connect Pixelixe to Claude

Use this guide for Claude custom connectors via remote MCP. It covers the owner and member split for Team and Enterprise, plus the simpler Pro and Max flow.

Open Claude guide

Connect Pixelixe to n8n

Use this guide if you want Pixelixe inside n8n workflows. It distinguishes the MCP Client node from the MCP Client Tool node so you pick the right setup path.

Open n8n guide

Connect Pixelixe to Make

Use this guide for Make scenarios. It follows Make's official MCP Client app flow, including the manual server URL path and the API key or OAuth options.

Open Make guide

Connect Pixelixe to Zapier

Use this guide if your Zapier environment exposes a third-party remote MCP setup surface. The page is intentionally conservative because Zapier's public docs are less explicit here than for Make or Claude.

Open Zapier guide

Before opening any connector UI

  1. Keep both auth paths in mind: OAuth is best for human-facing chat clients, while Bearer is often the fastest path in no-code workflow tools.
  2. Find your Pixelixe API key in your Pixelixe account settings in case the platform asks for a stored Bearer credential.
  3. Keep the MCP endpoint URL ready: https://studio.pixelixe.com/api/mcp/v1.
  4. Store the API key as a connector credential or secret, never in prompts, JSON bodies, or copied examples.
  5. Start with a read-only test first, such as reading tool docs or searching documents.

What is the best auth mode for each platform?

  • ChatGPT: prefer OAuth when the workspace exposes the Pixelixe sign-in flow. Use a stored Bearer secret only if your ChatGPT surface explicitly supports it.
  • Claude: prefer OAuth. Claude's custom connector flow is designed around the user connecting their own account.
  • n8n: Bearer is usually the fastest setup. OAuth2 is also possible if you want user-level sign-in.
  • Make: the fastest path is usually the API Key / Access token field. OAuth is an option if your Make flow exposes it.
  • Zapier: use whatever secure auth surface your Zapier product currently exposes for third-party remote MCP servers. Availability varies more here than on the other platforms.

Recommended first test

Once your connector is live, the safest first prompt is:

Use the Pixelixe connector only. First call pixelixe_get_tool_docs for pixelixe_search_documents, then search my saved documents and summarize the results in plain language.

That checks discovery, schema awareness, and human-friendly output without generating a new asset yet.

Official references used for these guides

Need the strict tool contract?

Open the technical MCP reference when you need exact schemas, validation rules, and output handling.

Open MCP docs