Port MCP Server
Connect Port to your AI agents with the Port MCP server.
Updated
What is Port MCP?
The Port MCP server is a Model Context Protocol server that connects Port to AI agents and assistants as a set of tools. With it connected, an agent can work with Port (internal developer portal — service catalog, scorecards, self-service actions) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Port tools become available to the model.
Connect the Port MCP server
Connect Port MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Port MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Port tool to confirm the connection is live.
Connect Port MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Port
Provide the Port MCP server URL or command and complete authentication.
- 3
Test
Reference Port from chat to confirm Cursor can reach the tools.
Sample use cases
A platform engineer checks service ownership gaps in the catalog
The agent queries Port's software catalog for services missing an owner or team assignment and posts a weekly 'orphan services' report.
A DevOps lead tracks deployment frequency per team
It reads Port scorecards and deployment entities, computes weekly deploy counts per team, and flags any team below the DORA threshold.
An SRE monitors production readiness checklists
The agent checks Port scorecards for services about to go live, identifies missing items (runbooks, alerting, load tests), and notifies the owning team.
A compliance agent audits infrastructure for policy violations
It queries Port blueprints for cloud resources missing required tags (cost center, data classification) and creates remediation tickets.
A new engineer onboards by exploring the service catalog
The agent searches Port for services related to their team, returns architecture diagrams, documentation links, and the on-call rotation.
A release manager tracks environment promotion status
It reads Port's environment entities to see which services have been promoted from staging to production and which are stalled.
An engineering manager generates a quarterly tech-debt report
The agent aggregates Port scorecard scores across all services, ranks the bottom 10 by maturity, and recommends remediation priorities.
Using Port MCP with Gamut
On Gamut, the Port MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Port and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What is the Port MCP server?
It is a Model Context Protocol server that exposes Port to AI agents as tools so they can work with it (internal developer portal — service catalog, scorecards, self-service actions).
How do I connect the Port MCP server?
Point your MCP client (Claude, Cursor, or Gamut) at the Port MCP server URL and complete authentication (OAuth). See the official documentation for the exact URL and scopes.
Can I use Port MCP with Gamut?
Yes — Gamut supports the Port MCP server, so your agents can use it as a tool in automated, triggered workflows.
What is Port?
Port is an internal developer portal that provides a software catalog, self-service actions, and scorecards for tracking service maturity and production readiness.
Does Port replace my CI/CD pipeline?
No. Port sits on top of your existing DevOps tools. It aggregates metadata from GitHub, Kubernetes, cloud providers, and CI systems into a unified catalog view.
Can Port enforce standards across microservices?
Yes. Port's scorecards let you define maturity criteria (documentation, alerting, test coverage) and track compliance for every service in the catalog.
How does the Port MCP server work?
The MCP server connects AI agents to Port's catalog, scorecards, and self-service actions through standardized tools, replacing manual portal navigation with automated queries.