# An Introduction to MCP and Authorization

**URL:** <https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130>\
**Category:** Blog Discussions\
**Tags:** mcp\
**Created:** [April 7, 2025, 9:50pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130 "2025-04-07T21:50:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertino.calcaterra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/robertino.calcaterra/32/66825_2.png) [@robertino.calcaterra](https://community.auth0.com/u/robertino.calcaterra)\
**Post date:** [April 7, 2025, 9:50pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/1 "2025-04-07T21:50:40Z")

</div>

Discover the Model Context Protocol (MCP) and its authorization mechanisms. Learn how to use API keys, OAuth 2.1 implementation, and best practices for secure LLM API connections.  
[Read more…](https://auth0.com/blog/an-introduction-to-mcp-and-authorization/)

✍🏻 Brought to you by @juan.martinez

 ![An Introduction to MCP and Authorization](https://global.discourse-cdn.com/auth0/original/3X/0/6/06cb0d66963f7e1f73ec7d9cbb9ad85324eab74a.jpeg)

---

<div class="post-metadata">

**Author:** ![robertino.calcaterra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/robertino.calcaterra/32/66825_2.png) [@robertino.calcaterra](https://community.auth0.com/u/robertino.calcaterra)\
**Post date:** [April 7, 2025, 9:51pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/2 "2025-04-07T21:51:09Z")

</div>

Seeking more information? Questions are welcome – ask away!

---

<div class="post-metadata">

**Author:** ![zablvit](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/zablvit/32/74667_2.png) [@zablvit](https://community.auth0.com/u/zablvit)\
**Post date:** [May 8, 2025, 4:34pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/3 "2025-05-08T16:34:43Z")

</div>

I think there is a mistake in the sequence diagram for 3rd party auth flow - the arrow nr 5 from the top (Authorization code) should go to MCP Server, not to 3rd party Auth Server - which is exactly the problem you’re describing 🙂

Great read! And apparently there is hope already - Issue 205 has just been resolved with an update to the spec.

---

<div class="post-metadata">

**Author:** ![bajcmartinez](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bajcmartinez/32/46418_2.png) [@bajcmartinez](https://community.auth0.com/u/bajcmartinez)\
**Post date:** [May 12, 2025, 5:53pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/4 "2025-05-12T17:53:20Z")

</div>

Hi @zablivt,

Thanks for reading. The authorization code goes to the 3rd party, the problem in the spec mentioned, is that the spec blurs the line between the resource server and the authorization server.

As for the new spec, I’m really looking forward to when that gets finalized. I’m sure I’ll write about it once it’s published.

---

<div class="post-metadata">

**Author:** ![joshcanhelp](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/joshcanhelp/32/74983_2.png) [@joshcanhelp](https://community.auth0.com/u/joshcanhelp)\
**Post date:** [May 26, 2025, 7:57pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/5 "2025-05-26T19:57:00Z")

</div>

Great read, as always!

In the How Does MCP Work? \> Your first MCP server section, we have a running MCP server but no example for the configuration in Cursor (or anywhere else). I see the sample config for the local file system but it would be nice to see how it looks for the remote server.

Thank you!

---

<div class="post-metadata">

**Author:** ![tom29](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/tom29/32/73774_2.png) [@tom29](https://community.auth0.com/u/tom29)\
**Post date:** [June 27, 2025, 10:45am UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/6 "2025-06-27T10:45:32Z")

</div>

how does multi-tenant authentication work with an MCP?

---

<div class="post-metadata">

**Author:** ![aishikpyne](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/aishikpyne/32/76166_2.png) [@aishikpyne](https://community.auth0.com/u/aishikpyne)\
**Post date:** [August 13, 2025, 5:46pm UTC](https://community.auth0.com/t/an-introduction-to-mcp-and-authorization/185130/7 "2025-08-13T17:46:48Z")

</div>

I want to understand the standard deployment processes for remote MCP servers.

Here’s my use case:

- I’m building a web app that runs LLM agents.
- I want **auto-discovery** of MCP servers and an **OAuth flow**.

The challenge:

- I have multiple users, each wanting to connect to their own Gmail account.
- Should I spin up **a separate Gmail MCP server process for each user** so that each instance only hosts one user’s credentials?
- That approach feels like overkill.

**Question:**

What’s the recommended architecture for this scenario?
