mcp catalogs are becoming the new internal developer portal

May 17, 2026 · 12:01 AM UTC ·7 min read · 0 reactions · 0 comments · 17 views

#mcp #platform engineering #ai agents #developer portals #governance

mcp catalogs are becoming the new internal developer portal

TL;DR · WeSearch summary

MCP catalogs are emerging as a new form of internal developer portal, providing agents with curated, governed access to tools and services similar to how humans use developer portals. Docker's recent release of Custom MCP Catalogs and Profiles enables organizations to standardize trusted tooling for AI agents using OCI artifacts. This shift mirrors past platform engineering trends, applying familiar patterns of curation, governance, and distribution to agent-driven workflows.

Key facts

▪Docker has introduced Custom MCP Catalogs, allowing organizations to bundle and distribute approved internal and public MCP servers as OCI artifacts.
▪Profiles in MCP Catalogs let developers switch between predefined sets of tools for different workflows, such as coding or planning.
▪Like internal developer portals, MCP catalogs provide structured access to capabilities, but are designed for AI agents rather than human developers.
▪By using OCI artifacts, MCP catalogs leverage existing container infrastructure for versioning, signing, and access control.
▪Profiles function not only as workflow organizers but also as implicit permission boundaries for different operational contexts.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/pvgomes/mcp-catalogs-are-becoming-the-new-internal-developer-portal-4aj1
Publication time	Sun, 17 May 2026 00:01:34 +0000
Retrieval time	2026-05-17T00:40:19.088Z
Last seen	2026-05-17T00:40:19.088Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	_d_B1TqRwScx
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 109646) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Paulo Victor Leite Lima Gomes Posted on May 17 mcp catalogs are becoming the new internal developer portal #ai #mcp #platform #governance Docker published a post on Friday about Custom MCP Catalogs and Profiles being generally available, and my first thought was not about Docker at all. My first thought was: this is Backstage, but for agents. Not literally, obviously.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments