# Org connectors Register your organisation's own MCP servers and REST APIs, and use them in chat. As an **org admin** you can register your organisation's own **MCP servers** and **REST APIs** as connectors, which let the assistant use outside tools and data in a conversation. Everyone in your org can then use them alongside the connectors PrivateMind provides. Both kinds are **external services reachable over HTTPS**. PrivateMind connects to them over the network, so there is nothing to install. - An **MCP server** speaks the [Model Context Protocol](https://modelcontextprotocol.io) (streamable-HTTP or SSE) and offers its own set of tools. - A **REST API** is a plain HTTPS host. The assistant can make `GET` requests to any path on that one host and can never write to it. ## Before you start You need two things: 1. **You are an org admin.** Regular members can't see Org Connectors, where you register connectors. 2. **The feature is on for your org.** On the [Organisation Settings](https://docs.privatemind.com/org-settings.html) page (`/settings/org/settings`), both of these must be **On**: - **MCP Servers** (the master switch) - **Custom MCP Servers** (allows your org to register its own connectors) When both are on, **Org Connectors** appears in the settings sidebar. ## Register a connector Open **Org Connectors** (`/settings/org/org-connectors`) and click **Add connector**. Choose the **Type** first, then fill in the rest: | Field | Notes | | --- | --- | | **Type** | **MCP server** or **REST API**. This is fixed once saved. | | **Name** | A label your members will recognise, e.g. "Acme Docs". | | **Server URL** / **API base URL** | The MCP endpoint (e.g. `https://mcp.example.com/mcp`) or the API host (e.g. `https://api.example.com`). Must be **HTTPS** and a **public** host. | | **Authentication** | For an MCP server: None, OAuth or Token. For a REST API: None, Basic or Token, with the credential supplied by the member who connects it. | | **Transport** *(MCP only)* | Streamable-HTTP, or SSE for a server that only speaks SSE. | | **Team access** | Everyone in the org, or one team. | | **Visibility** | Org-wide, or personal to you. | PrivateMind checks the URL when you save. It rejects plain HTTP and any host whose name resolves to a private or internal address, so a public-looking name that points inward is refused too. The type, URL, transport and authentication can't be changed after you save: to change them, remove the connector and register it again. A connector that a member requested is changed by that member through a change request, which an org admin approves in the Approval queue. Each org can register up to **25** connectors. ## What happens next: the status column The **Status** badge shows whether a connector is ready to use. After you add one, PrivateMind opens outbound network access from the platform to its host, called egress, and the badge follows that: | Status | Meaning | | --- | --- | | **Pending** | Registered. The network path to it is being requested. | | **Provisioning** | The egress path is being opened and applied. | | **Active** | Ready. It is reachable and now appears in the **Connectors Library** for your org. | | **Failed** | The egress path could not be opened. Remove and retry, or contact the PrivateMind team. | | **Disabled** | Turned off by an admin. Members no longer see it. | A connector a member requests waits in the **Approval queue** until an org admin approves or declines it. Declined requests are listed under **Declined**. The page refreshes by itself while a connector changes status, so you don't need to reload. > [!NOTE] > If a connector stays on **Pending** for more than a few minutes, egress for connectors (MCP egress) may not be enabled for your environment yet. This one-time platform step has nothing to do with your connector. Ask the PrivateMind team to enable it. ## Using a registered connector in chat Once a connector is **Active**, any member can find it: 1. In a chat, open the **+** menu and choose **Connectors**, or open **Connectors** from the top of the app. Go to the **Library** tab. 2. Registered connectors are listed there, **on by default**. A member can: - **Connect** it. This moves it into their **My Connectors** and, if it needs a personal key, saves that key. - Leave it, if they don't want it in their own chats. 3. Attach it to a conversation from the **Connectors** picker. The assistant can then call its tools or, for a REST API, make `GET` requests to it. To stop using a connector in a chat, open the **Connectors** pane at the top right of the conversation. Each attached connector has **Remove from this chat**, which detaches it from this conversation only, and **Delete connector**, which removes it from your connectors entirely. ## Managing connectors On the **Org Connectors** page each row has: - an **Enabled** switch, which turns a connector off for the whole org without deleting it. Turning it off closes its network access and members stop seeing it. Turning it back on sets it up again. - a **Remove** action, which deletes the registration and withdraws its access. ## Security and limits - **Trust.** An external connector receives whatever a member sends it during a conversation. Register only services your organisation trusts. - **Isolation.** Each org's registered connectors can reach only their own hosts, so one org can never reach another org's. - **Private data.** PrivateMind treats a registered connector as an untrusted path out of your organisation. If a conversation also holds a private, internal source, the external connector is dropped from that conversation so internal data can't leave through it. - **Public HTTPS only.** Registration rejects localhost, private IPs and plain HTTP. - **REST APIs are read-only.** A registered API is pinned to one host and to `GET`. ## Troubleshooting - **I can't see the Org Connectors page.** You must be an org admin, and both **MCP Servers** and **Custom MCP Servers** must be on in Organisation Settings. - **My connector is stuck on Pending.** Either MCP egress isn't enabled for your environment yet (see the note under the status table), or the host is unreachable. - **It registered but a member can't find it.** It appears in the Connectors Library only once it reaches **Active**. Check the status badge. ## Where next - [Organisation Settings](https://docs.privatemind.com/org-settings.html): the feature toggles that gate this page - [Connectors](https://docs.privatemind.com/connectors.html): how members find and use connectors in chat - [Users and teams](https://docs.privatemind.com/users-and-teams.html): who counts as an org admin