feat(portal): Publish MCP servers

[cloudjumpercat]

Description

Fixes #5086

Preview Links

• https://deploy-preview-5238--kongdeveloper.netlify.app/catalog/mcp-registry/#publish-an-mcp-server
• https://deploy-preview-5238--kongdeveloper.netlify.app/catalog/mcp-registry/#access-and-authentication
• https://deploy-preview-5238--kongdeveloper.netlify.app/dev-portal/#get-started
• https://deploy-preview-5238--kongdeveloper.netlify.app/mcp/#mcp-registry-tech-preview

Checklist

• Tested how-to docs. If not, note why here.
• All pages contain metadata.
• Any new docs link to existing docs.
• All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
• Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.
• Every page has a description entry in frontmatter.
• Add new pages to the product documentation index (if applicable).

[netlify]

✅ Deploy Preview for kongdeveloper ready!

Name	Link
🔨 Latest commit	6788dc6
🔍 Latest deploy log	https://app.netlify.com/projects/kongdeveloper/deploys/6a077c0b33ae7000071cc54d
😎 Deploy Preview	https://deploy-preview-5238--kongdeveloper.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

Updates the MCP Registry documentation and related landing pages to cover publishing MCP servers/registries into Dev Portal (tech preview), aligning with the Dev Portal MCP registry discovery work in #5086.

Changes:

• Expanded /catalog/mcp-registry/ to include Dev Portal as a publication target, with UI/API guidance and updated access/auth behavior.
• Updated the MCP landing page to mention publishing MCP servers to Dev Portal.
• Added a “Publish MCP servers” entry to the Dev Portal landing page “Get started” section.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
app/catalog/mcp-registry.md	Adds Dev Portal product metadata, publication instructions (UI/API), and updated auth/access guidance for internal vs Dev Portal consumption.
app/_landing_pages/mcp.yaml	Adds copy calling out optional publication of MCP servers to Dev Portal.
app/_landing_pages/dev-portal.yaml	Adds a “Publish MCP servers” CTA linking to the MCP Registry reference page.

Comments suppressed due to low confidence (3)

app/catalog/mcp-registry.md:121

• This section says “publish it (the MCP server) to a Dev Portal”, but the UI/API steps describe publishing an MCP registry; align the terminology so readers understand what is being published.

Optionally, publish it to a {{site.dev_portal}}:
{% navtabs "publish-to-portal" %}
{% navtab "UI" %}
1. In the {{site.konnect_short_name}} sidebar, click **Catalog**.
1. In the Catalog sidebar, click **MCP registries**.
1. Click the MCP registry you want to publish to {{site.dev_portal}}.
1. Click **Publish to portal**.

app/catalog/mcp-registry.md:169

• For clarity/grammar, replace “depends on if it's published …” with “depends on whether it's published …”.

How users and agents access and authenticate with your MCP server depends on if it's published internally in {{site.konnect_catalog}} or if it's published in a {{site.dev_portal}}:

app/catalog/mcp-registry.md:182

• For clarity/grammar, replace “depends on if the Dev Portal is set to be …” with “depends on whether the Dev Portal is set to …”.

Who can access the published MCP server depends on if the {{site.dev_portal}} is set to be [public or private](/dev-portal/portal-settings/#visibility).