Skip to content

Commit 3796ca6

Browse files
Hyperlint Automation Fix
1 parent 690ab6a commit 3796ca6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/docs/agents/model-context-protocol/authorization.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -126,14 +126,14 @@ Read the docs for the [Workers oAuth Provider Library](https://github.com/cloudf
126126

127127
If your application already implements an Oauth Provider itself, or you use [Stytch](https://stytch.com/), [Auth0](https://auth0.com/), [WorkOS](https://workos.com/), or authorization-as-a-service provider, you can use this in the same way that you would use a third-party OAuth provider, described above in (2).
128128

129-
You can use the auth provider to:
129+
You can use the auth provider to:
130130
- Allow users to authenticate to your MCP server through email, social logins, SSO (single sign-on), and MFA (multi-factor authentication).
131131
- Define scopes and permissions that directly map to your MCP tools.
132132
- Present users with a consent page corresponding with the requested permissions.
133133
- Enforce the permissions so that agents can only invoke permitted tools.
134134

135135
#### Stytch
136-
Get started with a [remote MCP server that uses Stytch](https://stytch.com/docs/guides/connected-apps/mcp-servers) to allow users to sign in with email, Google login or enterprise SSO and authorize their AI agent to view and manage their companys OKRs on their behalf. Stytch will handle restricting the scopes granted to the AI agent based on the users role and permissions within their organization. When authorizing the MCP Client, each user will see a consent page that outlines the permissions that the agent is requesting that they are able to grant based on their role.
136+
Get started with a [remote MCP server that uses Stytch](https://stytch.com/docs/guides/connected-apps/mcp-servers) to allow users to sign in with email, Google login or enterprise SSO and authorize their AI agent to view and manage their company's OKRs on their behalf. Stytch will handle restricting the scopes granted to the AI agent based on the user's role and permissions within their organization. When authorizing the MCP Client, each user will see a consent page that outlines the permissions that the agent is requesting that they are able to grant based on their role.
137137

138138
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/mcp-stytch-b2b-okr-manager)
139139

@@ -148,7 +148,7 @@ To set it up, first deploy the protected API endpoint:
148148

149149
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-auth0/todos-api)
150150

151-
Then, deploy the MCP server that handles authentication through Auth0 and securely connects AI agents to your API endpoint.
151+
Then, deploy the MCP server that handles authentication through Auth0 and securely connects AI agents to your API endpoint.
152152

153153
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-auth0/mcp-auth0-oidc)
154154

0 commit comments

Comments
 (0)