Aumo Docs

MCPs and Integrations

The two ways to give an Agent access to systems outside the platform.

Collections give the Agent something to read. Tools give it something to do: query a system, open a ticket, fetch data that changes by the minute.

AUMO offers two paths for this, MCPs and Integrations. Both follow the same design: a catalog in the Organization and an installation in the Workspace.

MCPs

MCP is an open protocol for exposing tools to AI models. An MCP server publishes a set of tools, and the Agent decides when to call them.

The path has two steps:

  • Organization › MCPs is the registry. That is where the company registers the allowed servers, from Docker Hub, from GitHub or from its own address.
  • Workspace › MCPs is the installation. Each workspace chooses which registry servers it wants to turn on, and gives each installation a name and a configuration.

The same registry server can be installed several times in the same workspace, as long as each installation has a different name. This allows, for example, two connections to the same system pointing at different environments.

Configuration and behavior belong to the installation, not to the registry entry. Changing one installation doesn't affect the others or the item registered in the Organization.

Integrations

Integrations are ready-made connections to well-known services, maintained by the platform. You don't describe the protocol: you pick the service from a list and provide the access.

They follow the same split. Under Organization › Integrations, the Available and Installed tabs show the known catalog and what the company has already registered. Under Workspace › Integrations, each workspace turns on the ones it will use.

In the workspace, the Integrations screen is accessible only to the Owner.

MCP or Integration

The choice is usually straightforward:

  • Use an Integration when the service is already on the list. It means less configuration, and the platform handles maintenance.
  • Use an MCP when the system is internal, specific to your business, or when you need to control exactly which tools are exposed.

It isn't an either-or decision: the same Agent can have MCPs and Integrations at the same time.

How the Agent uses the tool

In the Agent form, the MCPs and Integrations sections list what is installed in the workspace. You check what that Agent can call.

The MCPs section also has the maximum iterations: how many times, in a single answer, the Agent can call tools before it has to wrap up. This keeps an Agent from looping when a tool returns something unexpected.

An Agent only reaches what was installed in its workspace and checked in its form. Installing an MCP in the workspace doesn't automatically hand it to every Agent.

Credentials

Access to external systems lives under Organization › Credentials, stored once and reused by installations. Like Providers, the screen is restricted to the Superadmin.

This keeps the secret in a single place, while each workspace decides what to turn on without ever seeing the stored value.

Next steps

Providers and models

Where AI models come from, who enables them and how they reach an Agent.

Workflows

Automated flows built on a canvas, for when a task has fixed steps instead of a conversation.

On this page

MCPsIntegrationsMCP or IntegrationHow the Agent uses the toolCredentialsNext steps