read thedocs.

[ docs // guides & reference ]

Connector setup guides, tool references, auth flows, and platform concepts — everything you need to run StackJack, in one place.

Browse the Docs All Connectors
34 connectors documented // 6,712 tools referenced // setup, auth & platform guides
↓

No pages match that search. Clear it

← All documentation

Connect n8n and automation platforms to StackJack

For unattended automation — n8n, Make, Power Automate, Zapier, or plain webhooks — an API key is the simplest credential: a single sjk_… value you paste into one header. This page walks through n8n in detail and covers the header forms the other platforms need. (MCP is the Model Context Protocol, the open standard AI tools use to call external tools.)

Prerequisites

  • n8n 1.104 or later — the HTTP Streamable transport StackJack requires was added in n8n 1.104.0.
  • A StackJack API key. Creating one is restricted to an owner, co-owner, or Administrator, and requires typing an explicit risk acknowledgment — see Managing MCP credentials.
  • Your StackJack MCP endpoint URL: https://mcp.stackjack.io/mcp.

Connect n8n

  1. Create an API key. On the portal's MCP Setup page, click Create API Key and save the sjk_… value that is shown — it is displayed only once.
  2. Add an MCP Client node. In n8n, add the MCP Client Tool sub-node (inside an AI Agent) or the standalone MCP Client node — not a generic HTTP Request node.
  3. Set the endpoint and transport. Set MCP Endpoint URL to https://mcp.stackjack.io/mcp and Server Transport to HTTP Streamable (not SSE).
  4. Authenticate. Use Bearer Auth and paste your sjk_… key, or Header Auth with name X-API-Key and the key as the value.
  5. Scope the tools. Use the node's Tools to Include / All Except options to limit which StackJack tools the agent sees.

Per-user sign-in (alternative)

n8n 1.119 and later can connect with OAuth2 plus automatic client registration instead of a shared API key, so tool calls are attributed to a signed-in user. Versions 1.119–1.122 had registration bugs that were fixed in 1.123.0, so if you use OAuth2, run 1.123 or later. The API key remains the right default for unattended workflows, where there is no user to attribute calls to.

Make, Power Automate, Zapier, and webhooks

Any platform that can send a custom HTTP header can call StackJack. Point it at https://mcp.stackjack.io/mcp (Streamable HTTP transport, where the platform asks) and send the API key in either form:

Authorization: Bearer sjk_...

X-API-Key: sjk_...

Tool limits and scoping

Two layers of scoping work together:

  • In StackJack: the API key itself carries a tool selection — an admin picks the allowed tools when creating it (see Choosing tools for each client). Prefer a narrowly scoped key per workflow.
  • In n8n: the node's Tools to Include / All Except options further limit what the agent sees, without changing the key.

An unattended key is easier to leak than a sign-in connection — store it in your platform's credential vault or environment variables, never in workflow exports or source control, and rotate it if in doubt (rotation is available on the MCP Setup page).

Troubleshooting

  • Node errors about transport or connection — check Server Transport is HTTP Streamable, and your n8n version is 1.104+.
  • 401 errors — the key was mistyped, rotated, or revoked; also confirm you used one of the two header forms exactly (an API key cannot be used as Basic auth).
  • For anything else, see Connection troubleshooting.