Connect Pixelixe to Make

On this page

Before you start Setup steps First test Troubleshooting Official references

Other platforms

ChatGPT Claude n8n Zapier

Before you start

Make's official MCP Client app is one of the cleanest setup paths for Pixelixe, because it explicitly documents manual server URLs and saved credentials.

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

Authentication
The fastest path in Make is usually the API Key / Access token field with your Pixelixe API key. If Make offers an OAuth path for the server, you can use Pixelixe OAuth instead.

Setup steps

  1. Add the MCP Client module to your Make scenario and click Create a connection.
  2. Give the connection a name if you want.
  3. In the MCP Server field, choose + New MCP Server because Pixelixe is not one of Make's prefilled verified server entries.
  4. Enter https://studio.pixelixe.com/api/mcp/v1 in the URL field.
  5. If you are using manual auth, enter your Pixelixe API key in the API Key / Access token field.
  6. If you are using OAuth and Make asks you to configure a redirect URI on the server side, Make documents this callback: https://www.make.com/oauth/cb/mcp.
  7. Save the connection and authenticate if prompted.
  8. For the first validation step, use Make's Call a tool module before moving on to Execute an action with AI.

First test

A good first scenario is:

  1. Manual trigger
  2. Make MCP Client: Call a tool
  3. Tool name: pixelixe_get_tool_docs
  4. Arguments: {"tool_name":"pixelixe_search_documents"}

That matches Make's own recommendation to test a server with Call a tool before using the AI execution module.

Troubleshooting

  • If Make cannot connect, re-check that you used + New MCP Server and entered the exact Pixelixe URL.
  • If the connection works but auth fails, re-open the connection and verify whether you used the API Key / Access token field or an OAuth flow. Do not paste secrets into the task prompt.
  • If tool schemas look stale after a Pixelixe update, refresh or recreate the connection once so Make re-reads the current tool list.
  • If a later step does not render the generated asset, pass the returned URLs or inline image data explicitly to the downstream module.

Official references