Connect Pharlo to n8n

Status: Supported · Tested: No · Auth: OAuth 2.0 Bearer

n8n can call the Pharlo MCP server through an MCP Client node pointed at the Streamable HTTP endpoint.

⚠️

We have not yet run an end-to-end verification with n8n. The steps below follow n8n's documented MCP Client node; node names and OAuth handling vary by n8n version. For pure REST automation in n8n, the REST API with an ds_live_... key in an HTTP Request node is often simpler.

What you need

A Pharlo key (ds_live_...) from Settings → Credentials in the console (opens in a new tab).
An n8n version with the MCP Client node (or an HTTP Request node for the REST alternative).

Setup (MCP Client node)

Add an MCP Client node to your workflow.
Set the server transport to HTTP / Streamable HTTP and the URL:

https://pharlo.io/_mcp

Configure OAuth 2.0 credentials in n8n and complete the consent flow (enter your ds_live_... key on the Pharlo consent screen). n8n stores and refreshes the Bearer token.
Select a tool (e.g. list_connections, create_assignment) and map its inputs from previous nodes.

REST alternative (HTTP Request node)

For straightforward automation without MCP:

POST https://pharlo.io/api/v1/assignments
Header: Authorization: Bearer ds_live_...
Body (JSON): { "connectionId": "...", "type": "video", "payload": "{...}", "mediaUrl": "https://..." }

Note the auth difference: the REST API takes the ds_live_... key directly as a Bearer header. The MCP endpoint uses the key only on the OAuth consent screen and then short-lived OAuth tokens.

Troubleshooting

No MCP Client node — update n8n, or use the REST alternative above.
OAuth credential won't save — verify the discovery URL https://pharlo.io/.well-known/oauth-authorization-server is reachable from your n8n instance.

Limitations

MCP requests carry a 20% credit surcharge over direct REST calls — for high-volume n8n workflows, prefer the REST API.

ChatGPT Tool Reference