MCP

matic occupies both sides of the Model Context Protocol. As an MCP server, it exposes every platform capability — orgs, agents, tasks, decisions, runs — as tools that external AI systems can invoke. As an MCP manager, it registers external MCP servers and builds the canonical tool inventory that agent runtimes draw from during execution. These two roles are independent and run simultaneously, letting matic both control and be controlled through a single protocol surface.

Authentication

How matic authenticates inbound MCP connections and manages credentials for outbound connections to external MCP servers, including scope assignment at the org, team, and agent level.

MCP Manager

The subsystem that registers external MCP servers, resolves tool availability per agent, and supplies the canonical tool manifest to runtime adapters — without owning how each adapter materializes those tools.

MCP Server

The subsystem that exposes matic's CLI command surface as MCP tools, handling transport, sessions, capability negotiation, and request dispatch for external consumers.

Tool Manifest

The canonical tool inventory that aggregates tools from both matic's built-in capabilities and registered external MCP servers into a single, queryable surface consumed by every agent runtime adapter.

Tool Provisioning

The just-in-time flow that delivers tools from the manifest into an agent's execution context, bridging the gap between matic's runtime-agnostic tool registry and each adapter's native tool format.