MCP Manager

The MCP manager is the canonical source of tool availability for agents inside matic. It registers external MCP servers, manages their connections and credentials, resolves which tools each agent can access based on scope, and routes tool calls to the correct server at execution time. Everything an agent can do with external tooling flows through this component.

Server Registry

How external MCP servers are registered, stored, and resolved within a matic org — including metadata, capability declarations, and credential references.

Connection Lifecycle

The stages a server connection moves through from initial handshake to teardown, and how the manager maintains persistent sessions across agent tasks.

Health and Restart

How the manager detects unresponsive or degraded servers, applies retry policies, and restarts connections without disrupting in-flight agent work.

Namespace Deduplication

The strategy for resolving tool name collisions when multiple registered servers expose tools with identical names, and how qualified namespaces prevent ambiguity.

Scope Enforcement

How tool availability is filtered by matic scope — org, project, team, and agent — so that each agent only sees the tools its configuration permits.

Tool Routing

How inbound tool calls from agent runtimes are matched to the correct registered server and dispatched, including fallback behavior and error propagation.