Authorizing MCP node with OAuth

Feature Requests
,
1

The idea is:

Add an OAuth/OAuth 2 authorization type to the n8n mcp node.

My use case:

I am working for Apaleo where we are building a MCP-Server. Apaleo uses OAuth for authorization, and I currently do not see a clean way to authorize the MCP node (other then doing OAuth in a separate HTTP request)

I think it would be beneficial to add this because:

OAuth is more secure then just using bearer authentication, so I think there would be many Developers that would like to use it for their MCP. But that is only useful if the MCP Clients also support it.

Any resources to support this?

I can only speak from experience working for Apaleo on the MCP server, where authorization is one of our biggest headaches.

Are you willing to work on this?

Definitely, if there is anyone willing to have a look together with me into this issue
2

Hello @LReents,

We are facing the same ā€œissueā€ and would appreciate this feature to be added. I personally have an experience with N8N codebase as well as these auth mechanism, including the MCP and I am happy to make a contribution on that front personally.

Are you happy to schedule a chat/call together and discuss the requirements? We can merge both of ours requirements together and make a joint contribution, so can enjoy our MCP flows while using N8N.

I am based in Portland (OR) / US West Coast but super flexible when it comes into other timezones.

Radek

1 Like
3

Hey @radektomasek,
Happy to hear of other people willing to tackle this, Iā€™d be happy to have a chat with you.
My email is [email protected], feel free to contact me directly. I am based in Germany, so our time zones do not overlap too much, but I am also very flexible. Feel free to make a suggestion for Date and Time and I am sure Iā€™ll be able to make it work.
All the best,
Lennart

1 Like
4

@LReents sure thing, thank you for your quick reply. I am sure we will find some overlap (I am originally from the Czech Republic) therefore familiar with the specific timezone challenges.

I am going to write the mail now and letā€™s catch up sometimes next week and make this happen. :slight_smile:

2 Likes
5

Notion also offers a SSE MCP Server that requires an OAuth flow to authorize.

It was REALLY easy to make it work in Postman. I hope this will come to n8n soon.

image
image399Ɨ331 10.4 KB

image
image1119Ɨ616 63.1 KB

5 Likes
6

Hi @LReents , I am building auth tools for MCP at Civic - I am relatively new to N8N but tackling exactly this thing was next on my list. Iā€™d love to work with you to understand Apaleoā€™s use case! Would you be open to a chat about it?

1 Like
7

Hey Daniel, sorry for not responding so long, but it would be great to catch up with you.

Feel free to email me under [email protected], and we can schedule a call or something maybe? ^^

1 Like
8

Hi Lorents,

Iā€™ve sent you an email regarding this. Iā€™m currently experiencing the same issue and would appreciate the opportunity to discuss it with you. thanks !

9

This would be great, as it is really hurting n8n Cloud competitiveness:

cf. Using Atlassian MCP in n8n Cloud

Iā€™m working with multiple clients that wants those integrations. (Notion, Atlassian, etc.)
I personnaly prefer n8n Cloud.
But the absence of OAuth in the MCP authentication options negatively impacts:

  • time required to design business proposal for the client
  • time and cost per integration
  • complexity of agent tooling
  • complexity of workflows

Is anybody working on it?
I have 5 clients with whom Iā€™m preparing projects, if there is a roadmap to this, I can definetly sell it and use n8n in those projects, which I would love.

10

I need this badly too. OAuth is now the standard way to authorize MCP servers so itā€™s a must-have for N8N.

2 Likes
11

There are now multiple people working on this issue, and the more we get the better the chances of getting it published in the end. We have therefore set up a Slack Channel to create a sort of task-force for working on this issue, and if anyone would like to participate, please contact me and I will add you to the channel.

12

Hello, i would like to work on this issue because we what to run also a mcp server secured by oauth2. I tried to do a first draft of the code changes.

3 Likes
13

Thanks for your PR! Itā€™s a shame that nobody seems to be interested in reviewing it or giving some feedback at least, why this is the case.

2 Likes
14

Weā€™re waiting for this one as well. I hope itā€™ll get reviewed soon

1 Like
15

This is a big one for us as well, no oauth for n8nā€™s MCP client is really holding it back.

1 Like
16

This is holding us back as well.

17

ChatGPT requires OAuth (or no auth) for their beta MCP stuff to work.

18

Hellos guys, had a look at the PR and the approach sadly wonā€™t work. We created a demo internally and I think the nodeā€™s team in going to take to the finish like this quarter. No promises though.

1 Like
19

We Need OAuth for n8nā€™s MCP Server Trigger Node ā€“ Hereā€™s Why

The n8n MCP integration is powerful, but weā€™re hitting a wall: no OAuth support. Multiple companies building MCP servers (like Apaleo and Notion) are struggling with this limitation, as OAuth is their primary authentication method.

The Current Problem

The MCP Server Trigger node currently supports Bearer Auth, Basic Auth, and Header Auth, but no OAuth. This creates real blockers:

  • Enterprise tools wonā€™t connect: Services like Notionā€™s SSE MCP Server require OAuth flow to authorize

  • Security gaps: Static API keys donā€™t offer token refresh or granular permissions

  • Compliance headaches: No proper audit trails for regulated industries

Why This Matters NOW

Between February and April 2025, n8n officially introduced the MCP Server Trigger and MCP Client Tool nodes, positioning itself at the forefront of AI workflow automation. But without OAuth, weā€™re locked out of major integrations.

Real companies are blocked:

  • Apaleo canā€™t cleanly integrate their OAuth-secured MCP server

  • ChatGPTā€™s beta MCP requires OAuth or no auth

  • Atlassian integrations are stuck without OAuth support

What OAuth Would Unlock

// Imagine this in your MCP Server Trigger node:
{
  "authentication": "oauth2",
  "authorizationUrl": "https://provider.com/oauth/authorize",
  "tokenUrl": "https://provider.com/oauth/token",
  "scope": "read:data write:data"
}

This would enable:

  • Dynamic token refresh instead of static keys

  • User-specific permissions for multi-tenant workflows

  • Enterprise SSO integration

  • Compliance-ready audit trails

Community Progress

Good news: Multiple developers are already working on this, with a Slack channel coordinating efforts and a PR submitted. The n8n team has created an internal demo and indicated their node team might finish it this quarter.

What You Can Do

  1. Vote on the existing feature request: community.n8n.io/t/authorizing-mcp-node-with-oauth/130557

  2. Share your use case: Which OAuth providers do you need?

  3. Join the effort: Contact the community to join the Slack task force

The MCP protocol is transforming how AI agents interact with services. Letā€™s make sure n8n doesnā€™t get left behind because of a missing auth method.

Who else needs this? Drop your use case below! :backhand_index_pointing_down:

Tags: #oauth #mcp-server #feature-request #security

3 Likes
22

Hey team, is there any update on this?

1 Like