You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add VS Code GitHub Copilot integration docs for Keycloak OAuth
- Add "Use Keycloak OAuth MCP server with GitHub Copilot" section to README
- Add step-by-step instructions for connecting VS Code to deployed MCP server
- Include screenshots for authentication flow (allow access, sign-in, redirect)
- Add Spanish translation of the new section to spanish/README.md
- Configure VS Code redirect URIs in Keycloak realm for DCR support
- Update infra and keycloak configs for VS Code OAuth redirect handling
Copy file name to clipboardExpand all lines: README.md
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,6 +393,46 @@ This project supports deploying with OAuth 2.0 authentication using Keycloak as
393
393
394
394
The agent automatically detects `KEYCLOAK_REALM_URL` in the environment and authenticates via DCR + client credentials. On success, it will add an expense and print the result.
395
395
396
+
### Use Keycloak OAuth MCP server with GitHub Copilot
397
+
398
+
The Keycloak deployment supports Dynamic Client Registration (DCR), which allows VS Code to automatically register as an OAuth client. VS Code redirect URIs are pre-configured in the Keycloak realm.
399
+
400
+
To use the deployed MCP server with GitHub Copilot Chat:
401
+
402
+
1. To avoid conflicts, stop the MCP servers from `mcp.json` and disable the expense MCP servers in GitHub Copilot Chat tools.
403
+
2. Select "MCP: Add Server" from the VS Code Command Palette
404
+
3. Select "HTTP" as the server type
405
+
4. Enter the URL of the MCP server from `azd env get-value MCP_SERVER_URL`
406
+
5. You should see a Keycloak authentication screen open in your browser. Select "Allow access":
0 commit comments