---
title: "Britive MCP Gateway"
slug: "britive-mcp-gateway"
updated: 2026-09-21T12:37:25Z
published: 2026-09-21T13:28:34Z
canonical: "docs.britive.com/britive-mcp-gateway"
---

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

# Britive MCP Gateway

The Britive MCP Gateway is positioned between the AI initiating tool calls and the MCP servers that execute them. Every request is routed through the MCP gateway, which verifies whether the requesting identity is authorized, issues the backend a time-limited credential, and records the resulting activity.

The MCP Gateway does not work on its own; the following components must be installed and configured:

- **MCP Gateway**: This component is installed in your environment.
- **MCP Management**: An administrator connects the gateway to Britive and onboards MCP servers. For more information about details about different components and terminology, see [MCP Management](/v1/docs/mcp-management).
- **My MCP Servers**: This is visible only to the end users, where you connect to and use the MCP servers your administrator has already onboarded.

## 1. Install the MCP Gateway

Setting up the MCP Gateway is a two-step process:

1. Before installing a gateway, generate a gateway token from the platform. The gateway uses this token for authentication. For more information, see [Gateways](/v1/docs/mcp-gateways).
2. Install the Gateway and connect it using the token created from the Britive platform. For more information, see [Britive MCP Gateway](https://learn.britive.com/mcp-gateway/).
3. Run the diagnostic probe to confirm if the MCP Gateway is correctly connected. For more information, see [Troubleshooting](https://learn.britive.com/mcp-gateway/operations/troubleshooting).

At this point, the MCP Gateway is connected to the platform.

## 2. Onboarding MCP servers

An administrator uses the MCP Management to onboard MCP servers. There are two types of MCP servers, each with its own onboarding path:

- OAuth-based MCP server
  1. [Create an OAuth-based MCP server](/v1/docs/mcp-server#create-oauthbased-mcp-server)
  2. Use the **Sync Tools** option to get the tools in the catalog.
- Non-OAuth-based MCP Server
  1. [Create a non-OAuth-based MCP server](/v1/docs/mcp-server#create-nonoauthbased-mcp-server)
  2. The MCP gateway publishes the tools automatically; no manual step is required from the user.

After onboarding MCP servers, configure access policies by specifying members and tools. [Policies](/v1/docs/mcp-server#policies).

Now it is available to be authorized by users.

## 3. For end users: My MCP Servers

The administrator onboards an MCP server through the MCP Management; each user then connects to it individually. This applies to OAuth-based servers in particular; the administrators’s setup does not automatically authorize the user.

To start using an onboarded MCP server:

1. Go to [**My MCP Servers**](/v1/docs/my-mcp-servers).
2. Make sure the gateway is already connected from [Install the Gateway](/v1/docs/britive-mcp-gateway#1-install-the-gateway) step.
3. Authorize the MCP servers and tools you need.