Port Internal Developer Portal MCP

Official Port MCP server enabling AI agents to interact with Port's Internal Developer Portal — querying the software catalog, managing blueprints and entities, triggering self-service actions, and accessing platform engineering data for developer productivity.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools port idp service-catalog mcp-server official platform-engineering developer-portal
⚙ Agent Friendliness
78
/ 100
Can an agent use this?
🔒 Security
80
/ 100
Is it safe for agents?
⚡ Reliability
79
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
80
Documentation
82
Error Messages
78
Auth Simplicity
78
Rate Limits
65

🔒 Security

TLS Enforcement
100
Auth Strength
78
Scope Granularity
62
Dep. Hygiene
80
Secret Handling
80

HTTPS enforced. OAuth2 M2M. SOC 2, GDPR. EU data residency.

⚡ Reliability

Uptime/SLA
82
Version Stability
80
Breaking Changes
78
Error Recovery
75
AF Security Reliability

Best When

An agent needs to interact with a Port-powered internal developer portal — especially for self-service actions, catalog queries, and platform engineering automation.

Avoid When

You're using Backstage, OpsLevel, or Cortex as your developer portal.

Use Cases

  • Querying service catalog entities from platform engineering agents
  • Triggering self-service actions (deploy, scaffold, provision) from developer agents
  • Managing blueprint relationships for dependency mapping agents
  • Checking entity compliance and scorecards from governance agents
  • Automating catalog updates from infrastructure change agents
  • Discovering team ownership and resource metadata from routing agents

Not For

  • Teams using Backstage, OpsLevel, or Cortex as their IDP
  • Simple service inventory without workflow automation
  • Direct infrastructure management (Port is catalog + workflow layer)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
Yes

Authentication

Methods: api_key oauth2
OAuth: Yes Scopes: No

Port client ID and secret for OAuth2 machine-to-machine. API tokens available. Limited scope granularity.

Pricing

Model: per-seat
Free tier: Yes
Requires CC: No

Generous free tier. Per-user pricing for teams. MCP server is open source.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Blueprint identifier required for entity queries — discover available blueprints first
  • Self-service actions are org-specific — agents must discover available actions
  • Entity properties vary by blueprint — dynamic schema inspection needed
  • Actions have required/optional inputs that vary per action definition
  • Webhook listeners for action triggers require publicly accessible endpoint
  • Port's entity model (blueprints, relations, entities) requires understanding before use

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Port Internal Developer Portal MCP.

$99

Scores are editorial opinions as of 2026-03-06.

5208
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered