OAuth 2.1 Authentication for MCP Servers - Roadmap or workaround?

Questions
1

Hi Make community,

We’re currently using Make MCP Server to expose our scenarios via MCP, with servers identified by UUIDs. One challenge we’re facing is authenticating end users dynamically (e.g., via OAuth 2.1) before they access the tools exposed through our MCP servers.

Our goal:
Allow users to authenticate using OAuth 2.1 (or OAuth 2.0 with custom claims) so we can leverage external identity providers (Google, Microsoft, Auth0, etc.) and avoid managing static tokens or temporary codes.

Question:
Is there any plan to natively support OAuth 2.1 authentication for MCP servers identified by UUID in upcoming releases?
If not, has anyone implemented a proxy server or alternative solution to handle this authentication layer? We’d love to hear about your experiences or recommendations.

Context:

  • We’re using MCP Toolbox to expose tools to clients and collaborators.

  • Without OAuth 2.1, we’re considering building a proxy server to validate tokens before forwarding requests to Make MCP Server, but we’d prefer a native solution.

Thanks in advance for any insights or updates!
William

4

I brought up this topic. No response about it?

5

Hey @William_Gravier

Could you help me clarify one aspect so that I am sure I understand correclty: Do the end users have an account in your Make instance? Or are you also talking about external end users?

Thank you,
German

6

They don’t have account on my make instance. I just want to give them access some tools but I need to authenticate them.

7

To provide an honest answer: There are currently no plans to offer such a mechanism. We will keep an eye on the topic though.

8

Thank you for you answer,I will integrate my own IDP to handle user authentication between the LLM and the Make MCP servers so.