Skip to content

Commit 98e6a2f

Browse files
authored
Copy edit to auth section of remote MCP server guide (#21019)
1 parent 1f62c31 commit 98e6a2f

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

src/content/docs/agents/guides/remote-mcp-server.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -99,9 +99,7 @@ Learn more about other ways of using remote MCP servers with MCP clients here in
9999

100100
The example MCP server you just deployed above acts as an OAuth provider to MCP clients, handling authorization, but has a placeholder authentication flow. It lets you enter any username and password to log in, and doesn't actually authenticate you against any user database.
101101

102-
In the next section, you will add a real authentication provider to your MCP server. Even if you already have an authentication provider in place, following these steps will show you more clearly how to integrate it with your MCP server.
103-
104-
We'll use GitHub as the authentication provider here, but you can use any OAuth provider that supports the OAuth 2.0 specification, including Google, Slack, Stytch, Auth0, and more.
102+
In the next section, you will add a real authentication provider to your MCP server. Following these steps will show you more clearly how to integrate it with your MCP server. We'll use GitHub in this example, but you can use any OAuth provider that supports the OAuth 2.0 specification, including Google, Slack, Stytch, Auth0, and more.
105103

106104
### Step 1 — Create and deploy a new MCP server
107105

0 commit comments

Comments
 (0)