Portkey MCP

What Portkey's MCP directory is

Portkey publishes a browsable map of protocol servers grouped by category, sitting alongside its gateway, guardrails and observability products. It is partly a public directory and partly a funnel into the company's own gateway, which shapes both what is listed and why.

What it does

You scan a large list organised into data and storage, cloud and infrastructure, development tools, content and search, AI and memory, productivity, and system utilities, each with a short description and a link either to Portkey's own integration guide or to the upstream project. The loop is browse, read, integrate.

Many remote entries carry a link to try them through a hosted playground, and well-known vendors such as design, payments, monitoring and project tools appear alongside community projects. The company behind it sells a gateway with observability, guardrails and a managed gateway for these servers, and displays a compliance claim on its platform.

Who it is for

It is aimed at developers and teams surveying available servers, and at organisations already using the vendor's gateway products who want discovery and routing in one place. Platform teams that need per-server logging and access control get the most from the surrounding product.

What to keep in mind

Browsing is free with commercial products behind the company's own plans, so confirm what the gateway costs before assuming the directory is the whole offer. Directories maintained by vendors with adjacent paid products should be read with that relationship in mind, which is a statement about incentives rather than about honesty.

Two things deserve attention. The catalogue mixes first-party integration guides with raw upstream links, so the depth of vetting varies entry by entry and a consistent-looking list hides inconsistent effort. And a banner states the company has become part of a larger security vendor's gateway, which can change product naming, support arrangements and roadmap; confirm what you are buying now rather than what the documentation described last year.

The compliance badge refers to their platform rather than to any listed server. That distinction matters: a badge on the site tells you about the vendor's own controls, and nothing about the third-party code you are about to run.

Verify per-entry provenance, treat hosted playgrounds as environments where your inputs travel, and confirm the price and the terms before committing. A final point about directories attached to paid products: the free catalogue and the commercial platform are one strategy, which is not a criticism so much as a reading instruction. Use the map to find candidates, then evaluate each on its own repository rather than on how well it is described here, because the description exists to help you integrate and not to help you decide.