> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nexalytica.com/llms.txt
> Use this file to discover all available pages before exploring further.
# MCP Servers and Third-Party Integrations in Nexalytica
> Enable providers, connect your accounts, and register custom MCP servers so your Nexalytica agents can act on external SaaS tools — not just read your own data.
**MCP & Integrations** is where you connect Nexalytica to the external SaaS tools your team already uses — so your AI agents can act on them, not just read your own data. "MCP" stands for the **Model Context Protocol**, the standard connector Nexalytica speaks to reach those outside services. The page has two stacked sections: **Providers** (the catalog of tools you can connect) and **Connections** (the accounts already connected).
There are two separate ideas here, and keeping them apart makes everything else clear:
* **A provider** is *what* you can connect to (for example, a SaaS tool your agents should be able to call). An organisation admin decides which providers are switched on for the whole company.
* **A connection** is *whose account* is used. Once a provider is enabled, individual members connect their own account to it — personal to them, to a department, or to the whole organisation. Your credentials are encrypted in a secure vault and are never shown again after you enter them.
***
## Providers
The Providers section is the catalog. Each provider appears as a card.
### What you can do here
| Control / Button | What it does |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Provider card | Shows the provider's name, a **Verified provider** or **Unverified provider** badge, its category, a short description, and how many connections exist at each scope (or "Not connected"). |
| **Enable / Disable** switch *(admins only)* | Turns a provider on or off for the whole organisation. Members can only connect to enabled providers. |
| **Connect** / **Add connection** | Opens the Connect dialog to link an account. Labelled "Connect" the first time and "Add connection" once at least one connection exists. Disabled if the provider isn't enabled or isn't ready to connect. |
| **Add custom server**\*(admins only, top-right)\* | Opens the Custom server dialog to register your own remote MCP server. |
| **Custom** badge | Marks a provider your organisation added itself, rather than one from the standard catalog. |
| **Coming soon** badge | Appears on a provider that is listed but not yet connectable. |
Non-admins only see providers their organisation has already enabled; admins see the whole catalog.
***
## The Connect dialog
Opened from a provider's **Connect** / **Add connection** button. What it asks for depends on how that provider authenticates.
| Control / Field | What it does |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Connection scope** | Choose who the connection is for: **Personal** (only you), **Department** (a team you pick), or **Organisation** (everyone). The scopes you can choose depend on your role and what the provider allows. |
| **Department** picker | Appears only when you choose Department scope; selects which team the connection belongs to. |
| **API key / Bearer token** field | For providers that use a key or token. Entered as a password and stored encrypted in the credentials vault — never shown again. |
| **Requested access**\*(OAuth providers)\* | Lists the permissions the provider will be granted. Choosing **Authorise** sends you to the provider's own sign-in page, then returns you to Nexalytica. |
| **Connect** / **Authorise** | Creates the connection (or starts the OAuth redirect). Shows "Connecting…" while it works. |
| **Cancel** | Closes the dialog without connecting. |
When you authorise an OAuth provider, your browser is handed to that provider to sign in, then bounced back to a short **"Finishing connection…"** screen that confirms **Connected** and returns you to Integrations (or shows **Authorisation failed** with a reason if something went wrong).
***
## The Custom server dialog (admins)
Admins can bring their own remote MCP server instead of using only the standard catalog. The server's web address must be on an administrator-approved allow-list, and new servers start as "unverified".
| Control / Field | What it does |
| -------------------------------------------------- | ----------------------------------------------------------------------------- |
| **Name** | A label for your server. |
| **Base URL** | The server's address (must be allow-listed). |
| **Auth type** | How it authenticates: No authentication, API key, Bearer token, or OAuth 2.1. |
| **Category** | The kind of server, for grouping. |
| **Authorize / Token / Revoke URL, Default scopes** | Extra fields shown only when Auth type is OAuth 2.1. |
| **Description**\*(optional)\* | A short note about the server. |
| **Register server** | Adds the server as an organisation-private provider. |
***
## Connections
The Connections section lists every account connected across all scopes, as a table.
| Column / Control | What it shows or does |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Provider / Scope / Account | Which provider, at which scope (Personal / Department / Organisation), and which account. |
| Status | Whether the connection is healthy. |
| Last used | When an agent last used the connection ("… ago" or "Never"). |
| **Test** | Checks the connection is still working. Shows a spinner while testing. Only on connections you can manage. |
| **Revoke** | Opens a confirmation, then disconnects the account. This destroys the stored credential and agents lose access immediately — it cannot be undone. |
| **View only** | Shown instead of actions on connections you can see but not manage (for example, an organisation-scoped connection you didn't create). |
***
## How connections reach your agents
Enabling a provider and connecting an account doesn't automatically let every agent use it. A connected provider's tools still flow through the normal approvals:
1. An admin approves the tools under **AI Capabilities → Tools**.
2. Each agent is assigned the tools it may use.
3. When an agent runs, Nexalytica picks the right connection automatically — **personal first, then department, then organisation**. If no usable connection exists, that tool is simply left out of the run.
4. Removing someone from the organisation automatically revokes their personal connections.
***
## Who can use it
* Enable and disable providers for the organisation
* Add custom (bring-your-own) MCP servers
* Manage any connection, including organisation-wide ones
* Connect their own accounts to any provider the organisation has enabled, at a scope they're allowed to use
* Test or revoke the connections they manage
Everyone's credentials are encrypted in a secure vault and never displayed again after entry; only the people who can manage a connection can test or revoke it.