Skip to main content
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

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. 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”.

​
Connections

The Connections section lists every account connected across all scopes, as a table.

​
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.