Connect Pixelixe to n8n

On this page

Before you start Pick the right node Setup steps First test Troubleshooting Official references

Other platforms

ChatGPT Claude Make Zapier

Before you start

n8n exposes more than one MCP-related node, so the most important decision is choosing the right node for your workflow.

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

Authentication
n8n officially documents Bearer, generic header, and OAuth2 on its MCP client surfaces. For Pixelixe, Bearer is usually the fastest setup. OAuth2 is the cleaner path when you want each user to connect their own Pixelixe account.

Pick the right n8n node

  • MCP Client node: use this when you want Pixelixe tools as normal workflow steps. n8n documents this node with a remote MCP Endpoint URL, auth selection, tool selection, and JSON input mode.
  • MCP Client Tool node: use this when you want an AI Agent inside n8n to call external MCP tools. n8n's current public docs for this node still emphasize an SSE endpoint.
  • Recommendation for Pixelixe: prefer the MCP Client node for the most explicit official setup path, then move to the MCP Client Tool node only if your n8n build clearly supports the transport and auth combination you need.

Setup steps

  1. Add an MCP Client node to your workflow.
  2. Choose the remote server transport that your n8n version exposes for remote MCP servers.
  3. Set the MCP Endpoint URL to https://studio.pixelixe.com/api/mcp/v1.
  4. Choose your auth method. Use Bearer for the fastest setup or OAuth2 if you want user-level sign-in.
  5. If you chose Bearer, store your Pixelixe API key in the n8n credential. If you chose OAuth2, complete the Pixelixe sign-in flow.
  6. Select the Pixelixe tool you want to run. Use JSON input mode when the tool expects nested arguments such as modifications.
  7. Only after this direct node path is working should you wire Pixelixe into an AI Agent or a larger workflow.

First test

Start with a read-only workflow step such as listing tool docs or searching documents. A safe first call is:

Tool: pixelixe_get_tool_docs
Arguments:
{
  "tool_name": "pixelixe_search_documents"
}

Then chain a second call to pixelixe_search_documents and inspect the human-friendly presentation fields returned by Pixelixe.

Troubleshooting

  • If the MCP Client node cannot authenticate, re-open the credential and confirm the API key is stored as a Bearer token or that the OAuth2 flow completed successfully.
  • If your n8n setup only exposes the MCP Client Tool node and it still asks for an SSE endpoint, use a build that supports the MCP Client node for remote HTTP MCP servers before assuming the Pixelixe server is the problem.
  • If nested inputs fail validation, switch the node to JSON input mode instead of trying to flatten the payload manually.
  • If generation works but the image does not render downstream, pass the returned URLs or inline image data explicitly to the next node.

Official references