M MortelOS Docs

Version 0

MCP Runtime

Operate-mode MCP runtime boundaries for MortelOS host apps.

MortelOS has two AI surfaces:

Mode Purpose Tools
Build mode A coding agent assembles the host app from primitives. File edits, Artisan, Composer, tests and the setup-portal skill.
Operate mode A runtime agent operates the live workspace. OAuth-authenticated MCP tools served from the host.

The MCP server is not used for portal bootstrap. Bootstrap is code, config, Artisan and tests. MCP starts once the workspace is live.

Host mount

A host mounts the MortelOS MCP server from mortelos/framework in routes/ai.php:

use Laravel\Mcp\Facades\Mcp;

Mcp::oauthRoutes();

Mcp::web('/mcp/mortelos', config('mortelos.mcp.server'))
    ->middleware([
        'auth:api',
        // tenancy init from the MCP token
        // role resolution
        // trust-level enforcement
        // data classification
        // throttling
    ]);

Keep the route stable as /mcp/mortelos. Customer-specific MCP routes belong only in that host's own documentation.

What MCP exposes

The framework owns the operating-system level tool surface: entities, links, policies, workflows, inbox, skills, agent runs and context. Channel packages expose external data through connector actions and package contracts, not by changing the host route.

Every mutating MCP action needs:

  1. A policy ability.
  2. Tenant scoping.
  3. Actor resolution.
  4. Audit or event evidence.
  5. A clear failure mode when approval or runtime setup is missing.

Security rules

Concern Rule
Authentication OAuth 2.1 with dynamic client registration.
Tenancy Tenant context is initialized before framework tools execute.
Authorization The same policies govern web UI, widgets and MCP tools.
Trust Sensitive or mutating actions require the configured trust level.
Classification Data classification applies before agent-visible output.
Throttling Runtime tools should be rate limited per tenant and actor.

Do not expose new MCP tools from inside mortelos/starter. Starter is the host template. Reusable runtime behavior belongs in mortelos/framework or a package with explicit contracts.