Britive platform release 2026.08.02 is now live in production.

Press CTRL+K to open search

MCP Servers

Prev Next

You can configure two types of MCP servers:

  • OAuth-based MCP Server: This type of MCP server requires an external OAuth connection. Users need to sign in to access the MCP server. The MCP tools are discovered/synced with the Britive platform using OAuth credentials. Examples of OAuth-based MCP servers include Notion, Atlassian, GitHub, and Snowflake.

  • Non-OAuth-based MCP Server: This type of server does not need an OAuth connection. The authentication is performed by using a short-lived credential. The tools are discovered by the MCP gateway automatically, which reads them from the server. Examples of this type of MCP server are an internal database or an internal service.

For more information about both types of servers, see Backends.

Create an OAuth-based MCP server

  1. Log in to Britive.

  2. Click on System admin -> MCP Management. The page lists all MCP servers the user can access.

  3. Click the Create MCP Server button and enter the following details:

    1. Server Name

    2. Server Identifier: A unique identifier string for the MCP server, auto-generated from the server name.

    3. Description

    4. MCP Endpoint (Mandatory): Enter the HTTPS URL of an MCP server.

    5. Enable the OAuth-based MCP Server setting.

    6. Enter the following OAuth connection details:

      1. Callback URL: A callback/redirect URL where the OAuth provider sends the user back to after they've signed in. This URL is auto-generated; note down this URL, which is required to be configured in the OAuth server.

      2. Well-known URL (Optional): The URL that an authorization server publishes so clients can automatically discover login, token, and key verification URLs.

      3. Authorization Endpoint (Mandatory): The OAuth provider's URL that the user is redirected to in order to sign in and grant consent.

      4. Token Endpoint (Mandatory): The OAuth provider's URL that Britive calls to exchange an authorization code (or refresh token) for an access token.

      5. Registration Endpoint: If your provider supports OAuth Dynamic Client Registration (DCR), enter its registration endpoint so Britive can register itself as a client and obtain a Client ID and Client Secret automatically.

      6. Client ID: The client identifier issued by your OAuth provider—either issued directly by the provider or obtained automatically via the Registration Endpoint above. Enter a registration endpoint or a client ID, not both.

      7. Client Secret: The confidential secret issued alongside the Client ID, used to authenticate to the provider during token exchange.

      8. OAuth Scopes (Mandatory): The scopes to request from the provider, limiting what the MCP server can access on the user's behalf.

      9. Cloud ID: A unique site or tenant identifier used by cloud platforms (like Atlassian) to route API requests to a specific customer instance after authentication.

    7. Gateway: Select the gateway from the drop-down list. For more information, see Gateways. If no gateway is selected, any gateway with a valid token can access the MCP server.

    8. Credential Providers: Click Add Credential Providers to add credential providers to this MCP server. For more information about creating a credential provider, see Credential Provider. You can add only one credential provider per server.

    9. Click Create Server.

    10. Click Sync Tools to sync the tool catalog.

Create a non-OAuth-based MCP server

  1. Log in to Britive.

  2. Click on System admin -> MCP Management. The page lists all MCP servers the user can access.

  3. Click the Create MCP Server button and enter the following details:

    1. Server Name

    2. Server Identifier: A unique identifier string for the MCP server, auto-generated from the server name.

    3. Description

    4. MCP Endpoint (Mandatory): Enter the HTTPS URL of an MCP server. Make sure to have a URL resolvable from the MCP Gateway, with a certificate the gateway trusts.

    5. Disable the OAuth-based MCP Server setting.

    6. Gateway: Select the gateway from the drop-down list. For more information, see Gateways. The selected gateway can access MCP Server. If no gateway is selected, any gateway with a valid token can access the MCP server.

    7. Credential Providers: Click Add Credential Providers to add credential providers to this MCP server. For more information about creating a credential provider, see Credential Providers. You can add only one credential provider per server.

    8. Click Create Server.

    9. The tools are synced automatically by the gateway.

Manage MCP Servers

  1. Click the Manage icon to manage an MCP server:

    1. Details: This tab displays MCP server details, and the following actions are available:

      1. Edit: Edit MCP server details.

      2. Refresh Tools: Click to refresh the already discovered list of tools for the OAuth-based MCP server.

    2. Tools: This tab displays all the discovered tools of the MCP server, and you can view the schema of each of these tools to find out more details. Users can then configure an access policy controlling who or what can use it.

    3. Policies: See Policies.

Policies

Configure policies to allow users access to discovered tools.

The following actions are available for the listed policies:

  • Manage policy: You can edit, clone, disable, or delete a policy.

  • Enable/Disable policy: You can enable or disable any policy.

  • Clone policy: Make a copy of the existing policy to fine-tune as per your requirements.

  • Delete policy: Delete the customized policy. You cannot delete the predefined policies.

  1. Enable the Policy Prioritization setting to set the priority of policy evaluation. Prioritizing policies may change the policy execution and existing access for affected identities. Policies can be prioritized by dragging and dropping them from a list of policies, and the policy execution order is as shown on the UI. If this feature is disabled, the system's default policy evaluation is applied. Policy ordering determines deterministic precedence when multiple policies grant the same tool.

  2. Click on the Add Policy button to add a new policy.

  3. In the Add Policy tab, enter the following:

    • General

      • Enter the Policy Name.

      • Enter the description.

    • Members:  

      • Users: Click Select Users and add one or more members for this policy.

      • Tags: Click Select Tags and add one or more tags for this policy.

      • Service identities: Click Select Service Identities and add one or more service identities for this policy.

      • AI identities: Click Select AI Identities and add one or more AI identities for this policy.

    • Generic Conditions:

      • IP based: Select if you want access based on the IP addresses. Enter an IP address or a list of comma-separated IP addresses in the text box.
      • Time based: Select the Start and End Date/TimeDate-time range or Set Time Schedule for applying the policy.

    • Tools: Enable or disable the tools to grant access. By default, all tools are enabled.

    • Credential Providers: Click Add Credential Providers to add the credential provider that the tool needs for this policy. For more information about credential providers, see Credential Providers. A non-OAuth-based MCP server needs credential providers on the policy.

    • Click Save and Enable after all the configuration is done.

© 2026 Britive Inc. All Rights Reserved.