GitHub Remote MCP in Librechat using Oauth2.1 / GitHub App #8869
Replies: 3 comments 2 replies
-
Did you manage to solve it? I am trying same with Google Workspace MCP - https://github.com/taylorwilsdon/google_workspace_mcp, so far no luck |
Beta Was this translation helpful? Give feedback.
-
I never got it working - As a stop gap I've enabled the usage of the MCP server with a PAT for my users - Not as pretty as using Oauth, but at least it works. Was looking at trying the Workspace MCP as well, good to know that it also isn't working! |
Beta Was this translation helpful? Give feedback.
-
Note @mrh-chain that we do support additional OAuth fields if you want to try again with more in the configuration: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Trying to get the GitHub Remote MCP server running in the latest version (as of writing this) of LibreChat. I see in GitHub's documentation that the choice is between OIDC/Oauth2.1 or a PAT - Granted that I don't want users to have to provide a PAT, I've opted to use the Oauth2.1 solution.
GitHub mentions that in order to use Oauth2.1/OIDC one needs to provide a GitHub App or Oauth App for OIDC to work. I've created a GitHub App and configured LibreChat with this:
Both the ID and the Secret are available to LibreChat in its environment variables.
When starting LibreChat I see:
Later on, when trying to click the Authenticate button for the GitHub MCP Server in LibreChat, I see the following output in my logs:
Has anyone gotten this (Remote GitHub MCP with OIDC) working on LibreChat?
It seems weird that it tries dynamic client registration when I've already given it (LibreChat) access to a GitHub App client.
Beta Was this translation helpful? Give feedback.
All reactions