Port MCP
Description
Section titled “Description”Port is an internal developer platform (IDP) a software catalog and self-service action layer sitting in the External block of the Ikidna architecture. It models the organisation’s services, ownership, dependencies, and scorecards, and exposes self-service actions behind governance. The Port MCP server gives agents structured access to that catalog and to its governed actions.
Why It Matters for an Autonomous System
Section titled “Why It Matters for an Autonomous System”Port supplies two things an autonomous fleet needs:
- Organisation and ownership context. The catalog is a queryable source of project and repository context what services exist, who owns them, how they depend on each other, and their health scores. This feeds Ticket Enrichment and routing decisions with structured facts rather than re-derived guesses.
- Governed self-service actions. Port actions can wrap consequential operations (scaffold a service, request access, trigger a workflow) behind approval and policy, aligning with the Controls gate model an agent invokes a catalog action and the platform enforces who may approve it.
Surface and Constraints
Section titled “Surface and Constraints”Port MCP exposes catalog reads (entities, relations, scorecards) and constrained action invocations, routed and audited through the MCP gateway and logged to the Execution Ledger. Action permissions are scoped per Security.
Related
Section titled “Related”- Architecture - Port in the external services block.
- Context Layers - The catalog as project/repository context.
- Controls - Governed self-service actions as gated operations.
- Ticket Enrichment - Ownership and dependency context for intake.