Port MCP

Port's MCP server exposes an internal developer portal to AI clients, so the software catalog stops being a site someone has to visit and becomes context an agent can query directly. An assistant can search entities, follow the relations between them, read blueprint definitions to understand how the catalog is modeled, and answer ownership questions: which team runs a service, what it depends on, which environments it is deployed to, and where its documentation lives. Beyond reading, it can create and update entities, inspect or define scorecards that encode engineering standards, and trigger the self service actions a platform team has published, such as scaffolding a service or promoting one to another environment. Every operation runs under Port's role based access control, so an agent acting for a developer can only do what that developer could do in the UI, which is the condition most platform teams set before letting an assistant touch anything. The audience is platform engineering teams and the developers they support. For platform teams it makes catalog data and golden paths reachable from the IDE and from coding agents instead of only from the portal. For developers it removes the tab switch between writing code and finding out who owns the service they just changed. Security and governance functions use the same interface to check standards compliance in plain language.