SSO Authentication for Noibu MCP

Last updated: June 5, 2026

Overview

Noibu's MCP (Model Context Protocol) server supports Single Sign-On (SSO) authentication — customers can sign in to the MCP server using their company SSO provider (e.g. Okta, Azure AD).

Important: OAuth Flow Requirement

The Noibu MCP supports the CODE (Authorization Code + PKCE) flow only. The legacy IMPLICIT OAuth flow is not supported in the MCP (IMPLICIT has been deprecated by OAuth 2.1).

If your company currently uses the IMPLICIT flow for SSO in Noibu, you will need to switch to the CODE flow before SSO will work in the MCP. Contact your Noibu account team if you're unsure which flow you're currently using.

How to enable SSO for Noibu MCP

For SSO to work with the Noibu MCP, two things are required:

  1. Your Noibu console SSO configuration must be set to the CODE flow (not IMPLICIT).

  2. The following callback URL must be added to your SSO provider's Allowed Sign-In Redirect URLs list:

https://mcp.noibu.com/sso/callback

This is a one-time setup step. Once added, users at that company will see an SSO option when logging into the MCP server.

Note: The SSO option is visible to all users on the login page, but it will only work for companies that have SSO already enabled in their Noibu console. If SSO isn't enabled in the console yet, contact your Noibu account team to get that set up first before completing the steps below.

Setup Steps

  1. Check your SSO flow type — Log into the Noibu console and confirm your SSO is configured for the CODE flow. If it's set to IMPLICIT, switch it to CODE.

  2. Log into your SSO provider's admin console (e.g. Okta, Azure AD / Microsoft Entra).

  3. Find the Noibu application (or the relevant app configuration).

  4. Navigate to the Allowed Sign-In Redirect URLs or Login Redirect URIs section.

  5. Add the callback URL: https://mcp.noibu.com/sso/callback

  6. Save the changes.

  7. Users can now log into the MCP using SSO.