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

# Organization MCP Servers

> Enable catalog integrations for your organization and submit your own private MCP servers

> [!NOTE]
>
> Requires the **Integrations (MCP)** feature to be enabled for your organization. Ask your administrator if you can't see it.

Integrations connect 48° to the tools your company already uses, such as a wiki, a ticket tracker or a CRM. Each integration is an MCP server. Owners and Managers decide which servers are available in their organization. Members then connect their own accounts and use the tools in chats and assistants.

![Organization integrations](https://mintcdn.com/blackmountaingmbh/XFag3CE4nO-WN3UD/images/screens/en/admin/integrations.png?fit=max\&auto=format\&n=XFag3CE4nO-WN3UD\&q=85\&s=41f2aebb82f3af27b83c1bdd9c58a998)

## Open the integration settings

1. Open the profile menu in the sidebar and select **Workspace Settings**.
2. Under **Modules**, click **Integrations**.
3. If you administer several organizations, choose one under **Organization**.

Only Owners and Managers see this page. If it says **Not enabled for this organization**, contact BlackMountain support to have integrations switched on.

The page has two lists:

* **Your organization's servers**: private servers your organization submitted.
* **Public catalog**: servers BlackMountain offers to all organizations.

## Enable a catalog server

1. Find the server under **Public catalog**.
2. Turn on its switch.

The server now appears for all members on the **Integrations** page, where each member connects their own account. Turn the switch off to make it unavailable again. Toolsets that include a disabled server show it as **Not enabled in this org**, and its tools don't run.

### Servers that need setup

Some servers need your organization's own app with the provider before anyone can connect, for example an OAuth app. These show a **Setup required** badge, and members see **Waiting for admin setup**. Members can copy a link for you from the connect window. It opens this page with the right server.

To finish the setup:

1. Make sure the server is switched on, then click **Configure for this organization** next to it.
2. Copy the **Redirect URI**.
3. In the provider's developer console, register an app (sometimes called a custom connector or OAuth client) and enter the redirect URI as its redirect or callback URL. Follow the server's setup guide if one is linked.
4. Back in 48°, choose **This organization's client**, paste the **Client ID** and **Client secret**, and save.

Members can then connect with one click. The server shows a **Customized** badge.

For servers that use an API key, **Configure for this organization** lets you choose the **Header name** and **Prefix** that members' keys are sent with. Leave the fields empty to use the server default.

> [!WARNING]
>
> If you change or remove your organization's OAuth client later, members who connected with it have to reconnect. 48° tells you how many are affected.

## Submit a private MCP server

If a tool isn't in the catalog, you can register your own MCP server for your organization only.

1. Click **Can't find your integration? Request one**.
2. Fill in the form:
   * **Name** and an optional **Description** and **Icon URL**.
   * **URL** of the MCP server endpoint. It must be reachable over the internet.
   * **Transport**: **HTTP** or **SSE**.
   * **Authentication**: **None**, **API key**, **OAuth 2.0** or **Header**.
   * Under **Advanced settings**, the **Alias** is generated from the name. Change it only if you need a specific one. It can't be changed after submission.
3. Click **Submit for review**.

BlackMountain reviews each submission before it becomes available. The server appears under **Your organization's servers** with one of these statuses:

| Status | Meaning |
| - | - |
| **Pending review** | Waiting for BlackMountain. You can **Edit** or **Withdraw** it. |
| **Active** | Approved. Turn on its switch to make it available to members. |
| **Rejected** | Not approved. The reason is shown. Edit and resubmit, or withdraw it. |
| **Disabled** | Switched off by BlackMountain. |

For an approved OAuth server, manage its OAuth client with the **OAuth client** key button next to it.

### Delete a private server

Switch the server off first, then click **Delete**. Members' connections to it and its toolset entries are deleted too. You can submit it again later.

## How members use integrations

* Each member connects their own account or API key. Credentials are stored encrypted, per member and per organization. Nobody sees anyone else's connection.
* Members use an integration in chat by picking a toolset or an assistant that includes it.
* Content from an integration is sent to the AI model, and the model can act in the connected tool on the member's behalf.

> [!TIP]
>
> Start with a few read-only tools that many people need. Bundle them into a shared toolset, so members don't have to pick individual tools.

## Related

> [card] [Toolsets](https://docs.blackmountain.io/admin/integrations/toolsets.md)
>
> Bundle integration tools for assistants and teams.

> [card] [Google Workspace setup](https://docs.blackmountain.io/admin/integrations/google-workspace.md)
>
> Connect Gmail, Drive, Calendar and more.

> [card] [Microsoft 365 setup](https://docs.blackmountain.io/admin/integrations/microsoft-365.md)
>
> Connect Outlook, OneDrive, Teams and SharePoint.

> [card] [Connections](https://docs.blackmountain.io/integrations/connections.md)
>
> How members connect their accounts.


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