MCP Access is n8n’s instance-level MCP gateway. It turns your entire n8n deployment into a single MCP server that external AI clients can connect to via OAuth.

Instead of building individual MCP Server Trigger workflows, you simply toggle existing workflows to be “Available in MCP” and they become discoverable tools for any connected AI agent.

The setup is simple: go to any workflow’s settings and flip the “Available in MCP” toggle. That workflow becomes a tool that external AIs can discover and call. No special trigger nodes required. No per-workflow URLs to manage.

When to Use MCP Access

  • You want a single connection point for external AIs
  • You need OAuth authentication (e.g., connecting from ChatGPT)
  • You want to expose existing workflows without modifying them
  • You’re managing access centrally at the instance level

Think of it as the front door. One entrance, one bouncer, one clipboard. The AI shows up with OAuth credentials, the Gateway checks the list, and routes the request to whichever workflow the AI asked for.

⚠️ Improvement Request:

While it’s great that you can view and trigger workflows from this endpoint, what would make this even more helpful is the ability to create and delete workflows as well.

I see this as the Builders endpoint, but you can’t build workflows here. You may as well use the MCP Server Trigger, and create a sub-workflow that accepts as input JSON to create workflows, and in that same trigger add a tool thats a subworkflow to automatically get all workflows.

You can even create a subworkflow to delete workflows via id. Other than Oauth, that completely removes the need for this, and is already more powerful via the MCP Server Trigger method.

Related Posts

← Back to MCP Overview
MCP Access Deep Dive
MCP Server Trigger Deep Dive
MCP Node Deep Dive
MCP Client Tool Deep Dive