> ## Documentation Index > Fetch the complete documentation index at: https://docs.aperium.apps.hillspire.com/llms.txt > Use this file to discover all available pages before exploring further. # Custom integrations > Add a remote MCP server to Aperium so its tools become available to agents. ## What is an MCP server An **MCP (Model Context Protocol) server** is a small service that exposes a set of tools, resources, or prompts over a standard protocol. Aperium's agents call those tools at runtime to read data, run actions, and integrate with whatever system the server is wired to. Anything an agent can do beyond pure reasoning (querying a database, sending an email, looking up a record in your internal app) is, under the hood, an MCP tool call. ## How Aperium uses custom MCP servers Aperium ships with built-in MCP servers for common SaaS systems (Google Workspace, Microsoft 365, Slack, Salesforce, NetSuite, BigQuery, Onyx, and so on). When you have a system that isn't on that list, the typical answer is: stand up your own MCP server in front of it, and register it in Aperium as a **custom integration**. The server can be hosted anywhere your agents can reach over HTTPS, and can implement whatever auth model fits your environment (no auth for an internal-only network, or per-user bearer tokens for systems that need user identity). Once you've registered a custom MCP server, Aperium's agents see its tools the same way they see tools from any built-in connector. Permissions, audit logs, and tenant isolation all work the same way too. ## Adding a custom MCP server There are two places an admin can add a remote MCP server: the **Admin Console** (any time after first sign-in) and the **admin onboarding flow** (the first time you sign in). ## From the Admin Console In the Admin Console, switch to the **MCP Servers** tab. The tab lists every configured server. Click **+ Add MCP Server** in the top-right corner of the **MCP Servers Management** panel.
Admin Console MCP Servers tab with the Add MCP Server button highlighted in the top right of the MCP Servers Management panel.
Here's a closer look at the button: Close-up of the Add Integration and Add MCP Server buttons in the MCP Servers Management header. The **Basics** section describes how the server appears across Aperium. * **Display Name.** What admins and agent builders see (for example `My Amazing MCP`). * **Name (ID).** A short, stable identifier used internally (for example `AmazingMCP`). Pick something you won't want to rename later. * **Description.** Optional one-liner describing what the server is good for. * **Enabled toggle.** Decides whether the server's tools load into agent context immediately. Leave it on for normal use; flip it off if you want to register the server but keep its tools out of agent reach for now. Add New MCP Server dialog with empty Display Name, Name (ID), Description, Supported Template, and Remote URL fields, plus an Enabled toggle. The **Connection** section tells Aperium where the MCP server lives and how to authenticate to it. * **Supported Template.** The auth shape Aperium should use when calling the server: * **Remote HTTP MCP – No Auth.** For servers that live on a private network and don't require any token. Aperium reaches the server with no `Authorization` header. Best for in-cluster services that are already protected by NetworkPolicy. * **Remote HTTP MCP – User Bearer Token.** Aperium attaches each user's per-user token as a `Bearer` token. Use this when your MCP server expects user identity, for example to enforce upstream permissions per user. * **Remote URL.** The MCP endpoint URL. The path usually ends in `/mcp` (for example `https://my-amazing-mcp.com/mcp`). Validation runs when the server is saved, so the URL must be reachable from Aperium when you click **Create**. Add New MCP Server dialog with Display Name 'My Amazing MCP', Name (ID) 'AmazingMCP', a description, Supported Template set to Remote HTTP MCP - User Bearer Token, and Remote URL set to https://my-amazing-mcp.com/mcp. Aperium validates the endpoint, registers the server against your tenant, and reloads the MCP Servers list. The new server appears with its display name, identifier, status pill, and tool count once tools are discovered. From there it behaves like any other connector: agents can call its tools, the **Permissions** tab can grant group-level access, and the **Pencil** icon next to the row lets you edit or rotate settings later. ## From the admin onboarding flow If you're setting Aperium up for the first time, you can register custom MCP servers during the onboarding flow without leaving it. On the **Set your company's tools** screen, click the **Remote MCP Servers** tile. Set your company's tools screen with a grid of category tiles including Email, Calendar, Messaging, ERP, CRM, Analytics, and a Remote MCP Servers tile in the bottom row. A modal opens listing every custom server you've added so far. Click **Add remote MCP server** to open the form. You can repeat this step to add as many servers as you need. Remote MCP Servers modal with copy explaining customer-hosted servers and an Add remote MCP server entry with a plus button. The fields are the same as in the Admin Console flow, with one extra: the onboarding form also accepts a free-form **Description** that admins and users will see alongside the server. * **Display name.** Shown across the UI. * **Server key.** Stable identifier. Use lowercase with underscores (for example `customer_data_mcp`). * **Remote URL.** The MCP endpoint, typically ending in `/mcp`. * **Authentication.** Pick **Remote HTTP MCP – No Auth** or **Remote HTTP MCP – User Bearer Token**, matching what your server expects. * **Description.** Optional context shown to admins and users. Add remote MCP server form with fields for Display name, Server key, Remote URL, Authentication, and Description, plus Cancel and Add server buttons. Click **Add server** and the server is saved immediately so Aperium can validate the endpoint. When you're done adding servers, click **Done** on the previous modal to return to the onboarding flow. ## Editing a custom server later Whether you registered the server through onboarding or the Admin Console, you can edit it at any point from the **Admin Console, MCP Servers tab** by clicking the pencil icon next to the row. Aperium asks for confirmation before saving changes that would invalidate connected users (for example switching the auth template). Custom servers are non-system, so they can also be deleted from the same row when you no longer need them.