MCP Servers

Overview

MCP (Model Context Protocol) is the standard way AI assistants such as Claude, ChatGPT or Cursor use external tools. RevOS gives your organization one MCP endpoint. Add it to your assistant once and it gets:

RevOS tools — query your live semantic model. Always on, can't be removed.

Every MCP server you connect — for example GitHub, Linear or HubSpot, so your assistant can use their tools alongside your RevOS data.

You manage which servers are connected on the MCP Servers tab. Turning a server off, or removing it, immediately hides its tools from your assistant.

Where to find it

In the left sidebar, click Agents, then open the MCP Servers tab.

The tab shows your MCP endpoint at the top, followed by a card for every server: the built-in RevOS.ai server first, then the servers you connected.

Who can do what

Action	Minimum role
See servers and their status, copy the endpoint	Any member
Add a custom server by URL, edit, turn on/off, remove	Developer
Connect a server from the catalog	Admin

How to connect your AI assistant to RevOS

On the MCP Servers tab, find the Your MCP endpoint card.

Click the copy icon next to the address.

In your assistant's connector settings, add a custom MCP server and paste the address as the server URL.

For assistants configured with a JSON file (Cursor, VS Code, Claude Desktop), use the snippet under Or, in a config file and click the copy icon.

For a step-by-step walkthrough with the RevOS plugin in Claude, see Connect Claude & Cowork (MCP).

How to connect a server from the catalog

The catalog contains vetted servers with the connection details already filled in: GitHub, Linear, HubSpot, Customer.io, Context7 and DataForSEO. This requires the Admin role.

Click the Add a server card (last in the grid).

In the Add an MCP server panel, optionally filter by category using the chips at the top.

Click Connect on the server you want. Servers already connected show Connected and a View button that jumps to their card. A server marked Unavailable can't be connected in your environment.

Finish authorization — what you see depends on the server:

Sign in with the provider (Linear, HubSpot, Customer.io, DataForSEO): you are sent to the provider to approve access, then returned to the MCP Servers tab.

Paste a key (GitHub, Context7): a dialog asks for the secret — a GitHub personal access token or a Context7 API key. Paste it and click Connect.

The new server appears as a card with its status.

How to add a custom server

Use this for any MCP server that isn't in the catalog. Requires the Developer role.

Click Add a server, then Add a custom server at the bottom of the panel.

Fill in the form:

ID — a short identifier: lowercase letters, numbers and hyphens (for example my-server).

Name (optional) — display name shown on the card.

Server URL — the server's address, for example https://example.com/mcp. It must be a public http(s) address; internal or private network addresses are rejected. If the server uses OAuth, you are asked to authorize it after you connect.

Headers (optional) — click Add header to send a header with every request, such as an API key or access token. Values are hidden.

Enabled — when off, your assistant won't see this server's tools.

Click Connect.

Advanced settings (OAuth Client ID and Secret) are only for OAuth servers that can't register clients automatically. Most servers don't need them — leave them blank.

How to manage servers

Turn on/off — use the switch on the server's card. Off keeps the connection but hides its tools from your assistant.

Edit — click ⋮ on the card, then Edit. Saved header names are listed; saved values stay as they are unless you add new headers, and new headers replace all saved ones. For servers connected from the catalog the URL is fixed — to change it, remove the server and reconnect.

Remove — click ⋮, then Remove, and confirm. Your assistant loses access to the server's tools; the server itself isn't affected.

Check status — each card shows a health badge (see below).

Server status

Status	Meaning
Working	The server responds and its tools are available.
Auth failed	The server rejected the credentials. Check the key, token or headers, or reconnect.
Unreachable	RevOS couldn't reach the server. Check the URL and that the server is online.
Not an MCP server	The URL responds, but not as an MCP server. Check the address.
Not checked	No check has run yet.

A successful check also reports how many tools the server offers.

Frequently Asked Questions

Why can't I see the Add a server card?

Adding servers requires the Developer role, and connecting catalog servers requires Admin. Ask an organization Admin to change your role if you need it.

Can I remove the RevOS.ai server?

No. It is built in and always on, so your assistant always has access to your RevOS data.

I connected a server but my assistant doesn't show its tools.

Check that the server is switched on and its status is Working, then reload the connector in your assistant.

Is my data secure?

Secrets you enter (API keys, tokens, header values) are hidden in the form. Sign-in servers use OAuth, so RevOS never sees your password with the provider.

Connect Claude & Cowork (MCP)

User Roles & Permissions