pleaseai Port Internal Developer Portal
Use the Port MCP tools automatically when the user works with their Internal Developer Portal — the software catalog, scorecards, self-service actions, or any SDLC governance task on Port.io.
Regions
Port operates in two regions, exposed as two MCP servers in this plugin:
| Region | MCP server | Endpoint |
|---|---|---|
| US | port-us |
https://mcp.us.port.io/v1 |
| EU | port-eu |
https://mcp.port.io/v1 |
Use one region — whichever matches the user's Port account. If unsure which region they are on, call describe_user_details on each and use the one that authenticates, or ask. Do not duplicate calls across both regions.
When to Use
- Catalog discovery: list blueprints/entities, find services, owners, dependencies.
- Scorecards & quality: check scorecard rules, levels, and which entities pass/fail.
- Self-service: list and run self-service actions, then track their run status.
- Knowledge: answer questions about the org's software using
search_port_knowledge_sources. - Portal config: inspect the sidebar, manage folders and dashboard widgets.
How to Use
- Start with
describe_user_detailsto confirm the active org/region when context is missing. - Use
list_blueprints→list_entitiesto explore the catalog before answering catalog questions. - Use
list_scorecardsfor quality/compliance questions. - For self-service:
list_actionsto find the action,run_actionto execute, thentrack_action_runto monitor until completion. Confirm with the user before running any action that creates or changes infrastructure. - For org-knowledge questions, prefer
search_port_knowledge_sourcesover guessing.
Important Notes
- Authentication is handled by the Port MCP server's OAuth flow (
/mcpto connect). No API key env var is required. run_actionmay trigger real infrastructure changes — treat it as a write operation and confirm intent first.- Some MCP servers expose additional capabilities via
load_skill; call it to discover Port-specific guided workflows when available.