AI Interface

MCP

Interface

MCP

Status

Planned

Purpose

Make supported ASUME capabilities available to compatible agents and AI systems.

Works with

Maintained understanding

ASUME's MCP interface is the planned agent-facing interface to ASUME. It is intended to let compatible AI systems use supported company-understanding and objective capabilities without reconstructing the company state independently.

The interface will work from the maintained understanding ASUME already holds, subject to the permissions and capabilities available to the relevant workspace.

Agent access

MCP is intended to make supported ASUME capabilities available to compatible agents through the Model Context Protocol.

Depending on the capabilities available when the interface is released, an authorised agent may be able to:

Capability	Purpose
Use company understanding	Access supported parts of the maintained company understanding relevant to its task.
Use objectives	Work with supported objective-specific capabilities and outputs.
Ask ASUME	Ask questions against maintained company understanding.
Use available actions	Invoke supported ASUME capabilities made available through the MCP interface.

The agent does not receive unrestricted access to ASUME or to all information in the workspace. The capabilities and context available through MCP remain controlled by ASUME and workspace permissions.

One understanding across agents

An agent using MCP should not need to create and maintain a separate representation of a company before it can use ASUME.

A company can be explored in the ASUME application and later used by an authorised agent through MCP while both continue to work from the same maintained company understanding.

At a simplified level:

Company information → Maintained understanding → MCP → Agent

This allows ASUME to act as an understanding layer for compatible agents rather than requiring each agent to reconstruct company state from raw information independently.

API and MCP

API and MCP are both programmatic interfaces to ASUME, but they are intended for different kinds of integration.

Interface	Intended use
API	Applications and workflows call supported ASUME capabilities through defined programmatic requests.
MCP	Compatible agents and AI systems discover and use supported ASUME capabilities through the Model Context Protocol.

Both operate on the same underlying principle: ASUME maintains the company understanding; other authorised systems can use it through controlled interfaces.

Using API or MCP does not create a separate company understanding.

Access and permissions

MCP access will remain subject to the permissions and information available to the relevant ASUME workspace.

Connecting an agent does not automatically grant that agent access to every company, source, objective, or capability available in ASUME. The interface should expose only the context and capabilities the connected system is authorised to use.

Authentication, capability discovery, available tools, scopes, and other implementation details will be documented as MCP support is introduced.

Because MCP is planned, its final capabilities and technical interface may change before release.