> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oqoqo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP server sign-in

> Connect an MCP server that uses Sign in with provider, with automatic registration or your own OAuth app, and find Oqoqo's redirect URI.

Remote MCP servers configured with **Sign in with provider** use OAuth. Each team member connects their own personal account, and runs use the connection of whoever launched them. Before you can sign in, the provider must recognize Oqoqo as an OAuth client:

| Registration mode | How it works | What you do |
| - | - | - |
| **Automatic registration** | Dynamic client registration or client ID metadata document (most MCP servers) | Enter the **URL**, keep **Sign in with provider** selected, choose **Create & connect**, and sign in with the provider. |
| **Your own OAuth app** | Required by identity providers such as Okta, Microsoft Entra ID, Google, and GitHub | Register an app with your provider using Oqoqo's redirect URI, then paste its **Client ID** and **Client secret**. |

Your OAuth app only identifies Oqoqo to the provider; you still authorize with your own user account.

## Redirect URI

Add this exact callback URL to any OAuth app you register for Oqoqo:

```text theme={null}
https://app.oqoqo.ai/oauth/mcp/callback
```

The same URL applies to every MCP server and appears in the server's **OAuth app** section (and as `redirectUri` in the CLI and plugin).

## Connect with your own OAuth app

> [tab] Dashboard
>
> 1. Create an OAuth app with your provider using Oqoqo's [redirect URI](#redirect-uri).
> 2. Open **Manage → Tools → MCP servers** and select **New MCP server**.
> 3. Enter the server **URL** (authentication switches to **Sign in with provider**).
> 4. Expand **OAuth app** (or **Use your own OAuth app**), paste your **Client ID** and **Client secret**, and select **Create & connect**.
>
> ![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.](https://mintcdn.com/oqoqo/-uZBVqrwR0prXWMq/images/screenshots/mcp-oauth-app-create-light.png?fit=max\&auto=format\&n=-uZBVqrwR0prXWMq\&q=85\&s=48a74a7b8fcf57a46cb162baa7d1f51c)
>
> To add or update app credentials on a saved server, edit the **OAuth app** section under **Account** and select **Save and connect**.

> [tab] CLI
>
> Client IDs and secrets are entered only in the dashboard, while the CLI checks whether a server needs its own OAuth app and prints the `redirectUri` and setup link:
>
> ```bash theme={null}
> oqoqo mcp accounts detect-auth mcp_2e8b6f13
> ```
>
> `--output json` returns `registration` (`automatic`, `oauth_app_required`, or `unknown`), `redirectUri`, and `oauthAppConfigured` ([`oqoqo mcp accounts detect-auth`](https://docs.oqoqo.ai/cli/agents-and-models#oqoqo-mcp-accounts-detect-auth)).

> [tab] Plugin (MCP)
>
> Ask your AI assistant whether the server needs an OAuth app. It calls **Detect how an MCP server authenticates** ([`detect_mcp_auth_mode`](https://docs.oqoqo.ai/mcp-server/agents-and-setup#detect_mcp_auth_mode)) and returns `setupUrl` where you paste the credentials in the dashboard.
>
> ```text theme={null}
> Does our HubSpot MCP server need its own OAuth app? What redirect URI do I add to it?
> ```

If detection reports `unknown`, try **Create & connect** first; if the provider requires a pre-registered app, Oqoqo prompts you and opens the **OAuth app** fields automatically.

![Saved MCP server after a failed Connect, offering Set up OAuth app, with the Redirect URI, Client ID, Client secret, and Connect.](https://mintcdn.com/oqoqo/-uZBVqrwR0prXWMq/images/screenshots/mcp-oauth-app-set-up-light.png?fit=max\&auto=format\&n=-uZBVqrwR0prXWMq\&q=85\&s=143a1093e1555fc251b279fdde8edb36)

## Client authentication

All OAuth sign-ins use PKCE. When you provide a **Client secret**, Oqoqo sends it using the method the provider's metadata declares (`client_secret_basic` by default, or `client_secret_post`). Leave **Client secret** blank only for public PKCE clients allowed by the provider.

## Common problems

| Message or symptom | Fix |
| - | - |
| **This provider needs its own OAuth app.** | Register an OAuth app with `https://app.oqoqo.ai/oauth/mcp/callback` and enter its Client ID and Client secret. |
| Redirect URI mismatch or callback did not return | Confirm the provider app lists `https://app.oqoqo.ai/oauth/mcp/callback` with no trailing slash or typo, then reconnect. |
| **Sign-in didn't complete. Check the OAuth app's Client ID and Client secret…** | Verify both credentials in your provider console (most providers require the Client secret). |
| **The provider rejected Oqoqo's redirect URI.** | Add the redirect URI or ask your provider admin to allow Oqoqo. |
| **This version's saved values are not bound to its address.** | Open the server's **Tools** tab, verify the URL, and select **Refresh** ([Saved header values](https://docs.oqoqo.ai/experiments/tools.md#saved-header-values-and-the-server-address)). |

See [MCP server sign-in fails](https://docs.oqoqo.ai/reference/troubleshooting.md#mcp-server-sign-in-fails) for additional errors.

## Next steps

> [card] [Tools](https://docs.oqoqo.ai/experiments/tools.md)
>
> Manage MCP servers, skills, CLIs, and SDKs.

> [card] [Treatments (Toolsets)](https://docs.oqoqo.ai/experiments/treatments.md)
>
> Add your connected MCP server to a treatment.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.