Who it is for
Platform engineering teams running an internal developer portal on Port.
Overview
Port builds an internal developer portal around a catalogue it calls a context lake: services, their dependencies, ownership, scorecards, and health. The connector's described scope is querying that catalogue in ordinary language and executing self-service actions and workflows against it, with the platform's guardrails still applying.
Scorecard analysis is named specifically, which is the part of Port that measures services against organisational standards. Twelve tools are published at the partner tier with documentation available. The directory record carries no endpoint URL, so unlike most entries here there was no address to call at all.
Platform engineering teams running an internal developer portal on Port.
No endpoint URL appears in the directory record, so the twelve tools could not be reached, let alone listed, and the mix of catalogue reads and action execution rests entirely on the description.
Availability
Port IO is listed in the Claude connectors directory only. Port IO has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
Port IO publishes 12 tools to Claude. That is a mid-sized surface: 51.4% of the 1,253 Claude-listed connectors expose fewer.
The median Claude-listed connector filed under Developer Tools publishes 13, so this one sits one tool below its bucket's median, 50th of 95.
It falls in the 11-20 tools band, which holds 22.5% of the Claude directory.
Port IO's Claude listing does not publish an endpoint URL. 48 of the 1,253 Claude listings are in the same position: real listings with documentation but no URL in the directory record, so the endpoint has to come from the publisher's own docs.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
Port IO carries partner verification in the Claude directory, which 474 of 1,253 listings do (37.8%). That is a review step past self-publishing, not an Anthropic-built server.
In the publisher's words
Connect Port's context lake and software catalog directly to Claude. Query services, dependencies, and ownership using natural language. Analyze scorecards and service health. Execute governed self-service actions and workflows with built-in guardrails.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Nearby
Computer vision datasets, training, and inference on Roboflow
Claude
Application security risk context from an Apiiro deployment
Claude
Screen recordings turned into troubleshooting context
ChatGPT
CodeRabbit review workflows applied to current working changes
ChatGPT
Compile source and inspect assembly output without leaving the chat
Claude
Read-only access to a Dolphin Sistemas knowledge base
ChatGPT
This is an independent catalogue entry compiled by Node8 from Port IO's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Port IO, and inclusion here is not an endorsement.
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.