MCP Academy · 课时

MCP 中的 OAuth 流程

了解客户端如何获取受保护服务器所需的令牌。

MCP 中的 OAuth 流程 是 CoddyKit 上的免费 MCP Academy 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 MCP Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MCP Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Static Tokens Fall Short

A single shared token works for one user, but real apps have many. OAuth gives each client its own token without handing out one master secret. 🔑

OAuth in One Sentence

OAuth lets a client obtain a short-lived access token by proving its identity, instead of you mailing secrets around by hand.

The Three Players

There is the client that wants access, the user who approves it, and the authorization server that issues the tokens.

MCP Servers Advertise Auth

A protected MCP server can tell clients where to authenticate by exposing its authorization server metadata. Clients read it to start the flow.

The Authorization Request

The client kicks things off by sending the user to the authorization server to log in and grant consent.

User Grants Consent

The user reviews what access is being asked for and approves. Nothing is issued until that consent step happens.

Exchanging the Code

The authorization server hands back a short authorization code, which the client swaps for a real access token.

POST /token
grant_type=authorization_code
code=AUTH_CODE_HERE

The Access Token Arrives

The token endpoint returns an access token. The client then sends it as a bearer token on every MCP request.

{
  "access_token": "eyJhbGci...",
  "token_type": "Bearer",
  "expires_in": 3600
}

Tokens Expire on Purpose

Access tokens are short-lived. When one expires, the client must refresh or re-authenticate rather than reuse it forever.

Refresh Without Re-Login

A refresh token lets the client get a fresh access token quietly, so the user is not prompted to log in every hour.

The Server Just Validates

Your MCP server does not run the login screen. It only validates the access token it receives on each incoming request.

Quick Check

Trace one step of the flow.

Recap: Earn the Token

OAuth turns "share a secret" into "earn a token": consent, exchange a code, get a short-lived access token, refresh as needed. 🔄

常见问题解答

「MCP 中的 OAuth 流程」课时是免费的吗？

是的 — 「MCP 中的 OAuth 流程」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MCP Academy 课程的其余内容，请升级到 CoddyKit PRO。 MCP Academy 课程共包含 4 节课。

「MCP 中的 OAuth 流程」这节课中我会学到什么？

了解客户端如何获取受保护服务器所需的令牌。你通过在浏览器中直接运行的动手代码来练习 MCP Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 MCP Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 MCP Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「MCP 中的 OAuth 流程」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 MCP Academy 课中编写并运行代码吗？

能。每节 MCP Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 MCP Academy