Port MCP server
The Port MCP server is how LLMs, IDEs, and automated workflows consume your Context Lake without going through the Port UI or writing API calls by hand.
Connect Cursor, Claude, GitHub Copilot, or any MCP-compatible client to Port and use natural language to query blueprints and entities, run actions, load skills, and work with the same catalog data that powers your portal.
What you can do
- Query the catalog in your IDE: ownership, dependencies, scorecard status, and entity details.
- Run Port actions from a chat or agent session when your role allows it.
- Build and update catalog resources with developer MCP tools (entities, actions, scorecards, and more depending on your permissions).
For installation, supported clients, authentication, and the full tool list, see Port MCP server overview and installation.
How this relates to AI agents
Port AI agents and the Port MCP server use the same underlying Port MCP tools. The difference is mostly who invokes them and where:
| Port MCP server | Port AI agents | |
|---|---|---|
| Typical caller | Developers in IDEs, external MCP clients, CI jobs | Systems, webhooks, APIs, orchestration |
| Interaction style | Conversational, ad hoc | Domain-specific, autonomous, machine-to-machine |
| Best for | Exploring the catalog, building in Port from your toolchain | Automated workflows (incident response, remediation, scheduled analysis) |
You can use the MCP server on its own. When Port AI agents are configured, the MCP server can also invoke them, but core catalog query and action tools do not require agents.
Port AI (assistant, API, Slack) uses the same tool surface for human-facing and programmatic AI access.
Ingestion vs. consumption
| Direction | Interface | Purpose |
|---|---|---|
| Ingest | Port MCP in ingestion | Create or update entities from an agent or IDE workflow |
| Consume | Port MCP server (this page) | Read and act on catalog data from external AI tools |
For live data that is not modeled in the catalog, pair MCP consumption with MCP connectors. See Integrations vs. MCP connectors.