Guides / Connect an AI client

Connect n8n to Zorlya

How n8n's MCP Client Tool node and its MCP OAuth2 credential line up with Zorlya's OAuth 2.1 server, and what the n8n docs leave unconfirmed.

4 min read. Updated .

Upload your resume

n8n can reach Zorlya at https://mcp.zorlya.com with its MCP Client Tool node, but we cannot confirm that the connection works. n8n documents only an SSE endpoint, Zorlya answers only Streamable HTTP, and n8n is not on Zorlya’s list of AI apps.

Limit today: n8n’s documentation for the MCP Client Tool node names only an “SSE Endpoint” field. Zorlya answers only Streamable HTTP: a GET to the address returns 405 and there is no event stream. The n8n docs do not say the node can use Streamable HTTP, so we cannot tell you this connection works. The OAuth half does match: n8n has an “MCP OAuth2” credential that supports dynamic client registration.

Not on Zorlya’s list yet. Zorlya accepts only the AI apps on its list: Claude, ChatGPT, Claude Code and Cursor (how it works). n8n is not on it, so Zorlya refuses its registration unless n8n sends you back to an address that a listed app uses. We have not tried it. The steps below are what n8n’s own documentation describes for a remote server.

What you need

  • A Zorlya account that is approved. A job seeker account needs the Pro plan, because AI client access is part of Pro.
  • An n8n instance with the MCP Client Tool node.
  • An MCP server that supports OAuth2. The n8n credential page says this is required.

Steps

  1. Add the MCP Client Tool node to an AI Agent in your workflow.
  2. Set SSE Endpoint to https://mcp.zorlya.com. This is the only endpoint field the docs list.
  3. Set Authentication to OAuth2 and create the MCP OAuth2 credential.
  4. Leave Use Dynamic Client Registration on. It is on by default, and n8n then registers itself with the server under RFC 7591, so you enter no Client ID and Secret. Leave Resource URL empty and n8n discovers it from the server.
  5. Connect the credential. On Zorlya’s Connect page, choose the account and the permission level, and sign in. Read only is the default. Choose Read and change if you want the write tools.
  6. In Tools to Include, pick All, Selected or All Except.

The redirect URI

Zorlya accepts a redirect URI only if it is https, or http on localhost or 127.0.0.1. n8n shows its OAuth Redirect URL in the credential, and its docs say registration fails if the server does not accept that URL exactly as displayed. A self-hosted n8n reached over plain http on a real host name or IP address will be refused at registration. Use an https address for n8n.

What you should see

The credential shows as connected, and the node lists Zorlya tools such as top_matches and search_jobs. If it does not, see below.

Example workflow idea: a daily digest

  1. A Schedule Trigger runs each morning.
  2. An AI Agent node gets the MCP Client Tool node attached.
  3. The agent’s instruction: call top_matches, keep the 5 highest scores, and write one line per job with the title, company and score.
  4. A Slack or Email node sends the text to you.

Use Read only for this. The workflow never needs the write tools. Zorlya allows 120 reads a minute per account, far above what a daily digest uses.

If it does not connect

  1. Transport. The node documents SSE only, and Zorlya has no event stream. This is the most likely cause and we could not confirm a way around it.
  2. Redirect URI. Registration is refused when n8n’s redirect URL is plain http on a real host.
  3. Expired sign-in. Access tokens last 1 hour and refresh tokens 30 days, rotating on use. After 30 days without a run, sign in again.

What we checked

The steps come from n8n’s documentation, read on 2026-10-17. We did not try the connection to Zorlya in n8n. The node page does not mention Streamable HTTP, a plan requirement or a version requirement, and the credential page does not say which transport or server URL format to use.

For the server side, see the developer page and security.

Sources