10 Essential Insights into Custom MCP Catalogs and Profiles for Enterprise AI

As organizations accelerate their adoption of AI tooling, managing the Model Context Protocol (MCP) servers has become a critical challenge. The launch of Custom Catalogs and Profiles marks a turning point for enterprise teams seeking control, flexibility, and scalability. These two features work together to streamline how you package, distribute, and share MCP servers—reducing friction for developers while ensuring governance and trust. In this article, we break down the ten most important things you need to know about these innovations, from creating your own curated catalogs to leveraging portable profiles. Whether you are a platform engineer or a frontline developer, these insights will help you harness MCP effectively.

1. Custom Catalogs Are Your Enterprise Toolkit for MCP Server Management

Custom Catalogs allow organizations to curate and distribute a vetted collection of MCP servers—no more hunting across the open internet. Instead, teams can rely on a centralized, approved set of tools. This approach brings together servers from Docker’s MCP Catalog, community sources, and internally built servers. The result is a single source of truth for AI tooling that balances flexibility with security. By defining which servers are authorized, IT departments can reduce risk while empowering developers to innovate. With Custom Catalogs, the days of ad‑hoc server discovery are over; you now have an enterprise‑grade repository that scales with your needs.

2. Profiles Make MCP Server Configurations Portable Across Teams

MCP Profiles introduce a new primitive that lets you define named groupings of MCP servers. Think of a profile as a reusable configuration bundle—perfect for sharing a consistent toolset across projects, teams, or even individual developers. For example, you can create a “data‑engineering profile” that includes database connectors, ETL tools, and monitoring agents, then share it via a simple file. Profiles solve a long‑standing pain point: setting up MCP servers manually every time you start a new project. Now, you can package your preferred servers and their configurations, making collaboration seamless and reducing onboarding time for new team members.

3. How to Build Your First Custom Catalog: A Step‑by‑Step Overview

Creating a Custom Catalog is straightforward. Start by defining metadata for each server you want to include. For instance, you might create a YAML file like mcp-dice.yaml that specifies the server name, title, type, image location, and description. Next, assemble a catalog file that references these servers along with any from the Docker MCP Catalog. You can then use the Docker CLI or Docker Desktop to import and publish your catalog. This process gives you full control over what goes into your curated list—whether it’s a custom dice‑rolling server or a third‑party integration. The entire workflow is designed to be developer‑friendly while meeting enterprise governance standards.

4. Combining Community and Custom Servers in One Catalog

One of the strongest features of Custom Catalogs is the ability to blend external and internal servers. You are not locked into a single source; you can pull servers from the Docker MCP Catalog, integrate community contributions, and add your own internally developed MCP servers. This hybrid approach ensures you leverage the best of both worlds—proven community tools and specialized, in‑house solutions. For example, you could include a popular weather API server from the community alongside a proprietary authentication server built by your team. The catalog becomes a living ecosystem that adapts to your organization’s evolving needs.

5. Profiles Eliminate Manual Configuration Drudgery

Before Profiles, each developer had to manually configure MCP servers for every project—a repetitive, error‑prone process. Profiles change that by allowing you to define a named grouping of servers once and reuse it infinitely. You can set up a profile that includes a database server, a logging server, and an authentication server, then apply it to any project with a single command. This not only saves time but also ensures consistency across your codebase. Profiles are especially valuable for large teams where standardization is key. They act as a portable package that travels with your project, making setup reproducible and predictable.

6. Importing Catalogs via Docker Desktop: A Developer’s Delight

While the CLI is powerful for automation, Docker Desktop provides a user‑friendly interface for importing and managing catalogs. After you publish your Custom Catalog, team members can easily import it through the Docker Desktop UI—no command‑line knowledge required. This lowers the barrier for adoption, especially for less technical stakeholders who still need access to approved MCP servers. The graphical interface shows all available catalogs, their contents, and version details. It’s a perfect example of how Docker is bridging the gap between developer productivity and enterprise manageability.

7. Security and Governance at the Heart of Custom Catalogs

When every team member could install any MCP server from the internet, security risks multiplied. Custom Catalogs give organizations the power to enforce a whitelist of approved servers. IT can curate only those servers that have passed security reviews, ensuring that no malicious or unvetted code enters the workflow. Additionally, catalogs can be versioned and signed, providing an audit trail. This governance layer is crucial for regulated industries where compliance is non‑negotiable. With Custom Catalogs, you maintain control without stifling innovation—developers still have the freedom to choose from a rich set of tools, but within a safe, managed environment.

8. Practical Use Cases: From CI/CD Pipelines to Developer Workstations

Custom Catalogs and Profiles shine in real‑world scenarios. In a CI/CD pipeline, you can use Profiles to automatically spin up the exact set of MCP servers needed for testing—no manual intervention. On developer workstations, a shared catalog ensures everyone uses the same trusted servers, reducing “works on my machine” issues. Another use case is multi‑team collaboration: a central platform team publishes a catalog of approved servers, and each product team creates its own profiles combining those servers with project‑specific ones. This layered approach scales naturally as your organization grows.

9. Profiles Lay the Groundwork for Future Enhancements

Docker designed Profiles as a flexible foundation that can evolve. Currently, they support static groupings of MCP servers, but the architecture is open to future features like dynamic profiles, conditional server loading, or integration with secret managers. The portable YAML format makes it easy to extend. For example, you might one day include environment variables or dependency definitions inside a profile. This forward‑thinking design means that investing in Profiles today prepares you for tomorrow’s advancements in MCP management. You are not learning a throwaway tool; you are adopting a building block for the future.

10. Getting Started: Your First Custom Catalog in Three Steps

Ready to dive in? Follow this quick start: (1) Create a metadata file for each custom server (e.g., mcp-dice.yaml). (2) Assemble a catalog JSON or YAML file that lists all servers—both custom and from the Docker MCP Catalog. (3) Use the Docker CLI command docker catalog import or the Docker Desktop “Add Catalog” button to bring it into your environment. That’s it. You now have a curated, shareable collection of MCP servers. Combine this with a Profile to define a reusable set, and you are set for efficient, enterprise‑grade MCP management.

Custom MCP Catalogs and Profiles represent a major leap forward in how organizations adopt and manage AI tooling. By combining curation, portability, and governance, these features empower teams to work faster and safer. Whether you are starting from scratch or scaling an existing MCP ecosystem, these ten insights give you the knowledge to make the most of the new capabilities. Dive in, create your first catalog, and experience the difference firsthand.