Your developer portal was built for a developer scanning docs in a browser: reading a page, copying a curl command, moving on. Increasingly, the thing reading those docs isn't a person. It's an agent, working through an API integration on someone's behalf. Point that agent at HTML built for eyeballs, and it scrapes what it can, misses what it can't, and eventually calls an endpoint that doesn't exist.

Today, Kong is introducing the **Portal MCP Server**: a dedicated MCP server for every Dev Portal, along with OAuth 2.0 connections, giving agents a governed way to discover and read a portal's pages and specs instead of scraping HTML.

Here's the new capability, plus a closer look at what's already shipped alongside it.

*right* page in a portal with hundreds, or thousands, of APIs is another problem entirely. Without an AI-native way to discover content, agents fall back on scraping and guessing, which means broken links, missed context, and content an agent was never supposed to see in the first place.

The Portal MCP Server solves this. Turn it on for a given Dev Portal, and agents can discover and read that portal's pages and specs, in code mode. As developers prompt for what they want to build, your Portal MCP Server will search for the appropriate APIs and generate code to call them.

Access still respects the portal's existing authentication and authorization policies. An anonymous agent sees exactly what an anonymous developer would see. An authenticated agent is bound to the same role-based permissions as the human it's acting on behalf of. Draft pages and restricted API specs and documentation stay exactly as hidden from agents as they already are from unauthorized people. This isn't a new access model bolted onto Dev Portal, it's the same governance you already trust, extended to a new kind of consumer.

Once you’ve opted into AI features, it's a single toggle per portal, not a project. No custom integration layer to build or maintain.

In your portal settings, you’ll now see a Connections section. Turn on OAuth 2.0 connections and any agent: Claude, Cursor, VS Code, or any other app you're building can connect to your Dev Portal the standard way. An Authorization Code flow with PKCE, endpoints discovered automatically, nothing to hand-configure. The developer logs in and consents once, and from there the agent is able to discover all APIs and content published, respecting the existing access controls. You control who gets in: trusted clients, an explicit allow-list of dynamic client registration (DCR) redirect URLs, or both. The same consent flow is ready to power any application you build that needs access to published pages or API specs.

The Portal MCP Server lands on top of several other Dev Portal updates that already shipped this year.

**Agent-ready markdown**

Even when an agent finds the right page, HTML gets in the way. Markup built for rendering in a browser such as nav bars, styling and embedded scripts buries the actual content an agent needs, leading to incomplete or garbled context and, downstream, hallucinated endpoints.

Now, any Dev Portal page can be fetched as clean Markdown instead of HTML, either with an Accept: text/markdown header or a .md URL suffix. Same page, same content, structured for a model instead of a browser.

**The Kong Konnect MCP Server now writes to Dev Portal**

The Kong Konnect MCP Server, the one customers already use for the rest of Konnect, now lets agents create, edit, and publish Dev Portal pages, snippets, and Markdown Components (MDC). Any MCP-compatible client, including Claude Code, Cursor, VS Code, and GitHub Copilot, can maintain portal content this way, governed by the PAT/SPAT permissions your team already manages. This results in one MCP touchpoint for all of Konnect, not a separate server per product.

**The Dev Portal Toolkit is now GA**

Every content change, whether human- or agent-made, used to mean a round trip through the hosted Portal Editor just to preview it. That slowed down the exact iteration loop teams needed to move faster on.

The [_Dev Portal Toolkit_](https://marketplace.visualstudio.com/items?itemName=konghq.vscode-konnect-dev-portal-toolkit)_Dev Portal Toolkit_, previously a download-only VS Code extension, is now formally generally available, letting portal builders and the agents working alongside them preview changes locally instead of waiting on the hosted editor.

As agents become a primary consumer of developer documentation, portals that aren't built for machine access get left behind. Dev Portal now is.

Turn on the Portal MCP Server in Kong Konnect today, or explore the rest of Dev Portal's AI enablement capabilities in[ _the documentation_](https://developer.konghq.com/konnect/) _the documentation_.