Skip to main content
An MCP server that uses Sign in with provider connects with OAuth. Each member connects their own account, and only that member can use the connection. First, though, the provider must know Obss as a client: The OAuth app only identifies Obss to the provider; you still sign in with your own account.

Redirect URI

The redirect URI (or callback URL) is where the provider sends you after you sign in. Add it to your OAuth app:
It’s the same for every MCP server. The dashboard shows it in the server’s OAuth app section, and the CLI and the plugin return it as redirectUri.

Connect with your own OAuth app

  1. Create an OAuth app with the provider, with the redirect URI.
  2. Open Manage → Tools → MCP servers and select New MCP server.
  3. Enter the server’s URL. Authentication changes to Sign in with provider.
  4. When the server needs an OAuth app, the OAuth app section opens with the Redirect URI and a copy button. On other servers, the same fields are under Use your own OAuth app.
  5. Paste the app’s Client ID. Add its Client secret if the provider gave you one.
  6. Select Create & connect, then sign in with the provider.
New MCP server form with Sign in with provider and the OAuth app section open: Redirect URI with a copy button, Client ID, and Client secret.New MCP server form with Sign in with provider and the OAuth app section open: Redirect URI with a copy button, Client ID, and Client secret.
To add or change the app on a saved server, open it, use the OAuth app section under Account, and select Save and connect.
unknown means the server didn’t publish how it registers clients, or Obss couldn’t read it. Select Create & connect anyway. If the provider needs an OAuth app, Obss tells you and opens the OAuth app section:
Saved MCP server after a failed Connect, offering Set up OAuth app, with the Redirect URI, Client ID, Client secret, and Connect.Saved MCP server after a failed Connect, offering Set up OAuth app, with the Redirect URI, Client ID, Client secret, and Connect.

Client authentication

When the app has a Client secret, Obss sends it the way the provider’s metadata says it accepts: Every sign-in uses PKCE.

Common problems

Obss sends the Client secret only to an address that a person chose. Learn more in Saved header values and the server address. For other connection messages, see Troubleshooting.

Next steps