# MCP server sign-in - Obss

Build treatments
MCP server sign-in
Connect an MCP server that uses Sign in with provider, with automatic registration or your own OAuth app, and find Obss’s redirect URI.
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:
How the provider knows Obss
What you do
Automatic registration
(most MCP servers), through dynamic client registration or a client ID metadata document
Select
Create & connect
and sign in. You don’t need app credentials.
Your own OAuth app
, required by many identity providers, such as Okta, Microsoft Entra ID, Google, and GitHub
Create the app with the provider, add Obss’s redirect URI, and paste its
Client ID
and
Client secret
in Obss.
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:
https://app.obss.app/oauth/mcp/callback
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
Dashboard
CLI
Plugin (MCP)
Create an OAuth app with the provider, with the
redirect URI
.
Open
Manage → Tools → MCP servers
and select
New MCP server
.
Enter the server’s
URL
.
Authentication
changes to
Sign in with provider
.
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
.
Paste the app’s
Client ID
. Add its
Client secret
if the provider gave you one.
Select
Create & connect
, then sign in with the provider.
To add or change the app on a saved server, open it, use the
OAuth app
section under
Account
, and select
Save and connect
.
You enter the Client ID and Client secret only in the dashboard. The CLI tells you whether a server needs an OAuth app, with the redirect URI and the dashboard link:
obss
mcp
accounts
detect-auth
mcp_2e8b6f13
For a server that needs one, it prints
Needs its own OAuth app.
, the redirect URI, and a link to the
OAuth app
section. With
--output json
:
registration
is
automatic
,
oauth_app_required
, or
unknown
.
redirectUri
is the address to add to the app.
oauthAppConfigured
says whether a Client ID is saved.
See
obss mcp accounts detect-auth
.
Ask your AI assistant how the server signs in. It calls
Detect how an MCP server authenticates
(
detect_mcp_auth_mode
), which returns the same
registration
,
redirectUri
,
oauthAppConfigured
, and
setupUrl
as the CLI.
Does our HubSpot MCP server need its own OAuth app? What redirect URI do I add to it?
You paste the Client ID and Client secret in the dashboard at
setupUrl
.
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:
Client authentication
When the app has a Client secret, Obss sends it the way the provider’s metadata says it accepts:
Method
When Obss uses it
client_secret_basic
The provider lists it, or lists no method. The secret goes in an HTTP Basic header.
client_secret_post
The provider lists it but not
client_secret_basic
. The secret goes in the request body.
Public client (PKCE, no secret)
You leave
Client secret
empty, so Obss sends only the Client ID. Do this only when the provider allows it.
Every sign-in uses PKCE.
Common problems
What you see
Cause and fix
This provider needs its own OAuth app.
The provider doesn’t register Obss itself. Create an OAuth app with the redirect URI and paste its Client ID and Client secret.
The provider’s page says the redirect URI doesn’t match, and doesn’t send you back to Obss.
Add
https://app.obss.app/oauth/mcp/callback
to the app exactly, then connect again.
Sign-in didn’t finish. If the provider showed a redirect URI error, …
The sign-in didn’t come back to Obss. Check that the app lists the redirect URI, then connect again.
Sign-in didn’t complete. Check the OAuth app’s Client ID and Client secret, then connect again.
The provider refused the app’s credentials. Check both values; many providers require the Client secret.
The provider rejected Obss’s redirect URI.
Add the redirect URI to the app, or ask the provider’s admin to allow Obss. An OAuth app can’t bypass the provider’s approval.
This version’s saved values are not bound to its address.
(with
Open Tools tab
in place of
Connect account
)
The server was saved at a new address, for example by an AI assistant through the CLI or the plugin. On the version’s
Tools
tab, check the address and select
Refresh
.
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
Tools
Create MCP servers, skills, CLIs, and SDKs.
Treatments (Toolsets)
Put your tools in treatments and keep a baseline.
Tools
Treatments (Toolsets)
Powered by
This documentation is built and hosted on Mintlify, a developer documentation platform