Skip to main content

​
Overview

n8n provides MCP support through its MCP Client Tool node for workflow automation.

​
Setup

1

Get your MCP URL from the dashboard

  1. Go to Connectors in the left nav and open the connector you want to use
  2. Click Use in Agent in the top right
  3. On the Use tab, click MCP Server under “Use with Agent Client”
  4. Select a linked account from the dropdown
  5. Choose HTTPS MCP as the client
  6. Copy the generated URL — it looks like:
The token encodes your account identity. No separate API key or account ID header is needed.
The token expires after one year. Regenerate it at any time using the refresh button in the MCP tile.
2

Add MCP Client Tool in n8n

  1. Create a new workflow
  2. Click + to add a node and search for “MCP Agent”
  3. Under tools, click + and search for MCP Client Tool
  4. Configure the node:
    • URL: Paste the URL from the previous step
    • Authentication: None
    • Select the tools you want from the Tools to include dropdown
3

Test the connection

Click Execute Step to verify the connection and see available tools.

​
Advanced: manual API key setup

If you prefer to authenticate with your API key and account ID directly instead of a dashboard-generated token:
  1. Set the URL to https://api.stackone.com/mcp?x-account-id=<ACCOUNT_ID>
  2. Set Authentication to Header Auth (create new credentials if needed):
    • Header name: Authorization
    • Value: Basic <BASE64_STACKONE_API_KEY> — base64-encode your API key followed by a colon (your_api_key:)
See Authentication & Security for details on obtaining your API key and account ID.

​
Building workflows

Once configured, use the MCP Client Tool node to execute StackOne actions on the linked account you specified.
For detailed n8n setup instructions, see the official n8n documentation.

​
Handling large tool catalogs

If the connector exposes many actions, add the tool-mode=search_execute query parameter to the MCP URL in your config. The client then registers just two tools — search + execute — and the agent discovers actions at runtime, so the context footprint stays flat however large the catalog:
For a token URL, append it as an extra parameter: https://api.stackone.com/mcp?token=<session_token>&tool-mode=search_execute. See Tool Discovery for how search works, its accuracy, and the other modes.

​
Optimize and secure

With your agent connected, use StackOne’s platform features to optimize performance and secure every call.

Search & Execute

Reduce context and save tokens.

Data Sync

Reduce latency and enable semantic search.

Defender

Block prompt injections before they reach your agent.