Your Guide to Custom MCP Catalogs and Profiles: A Q&A Breakdown

Welcome to our in-depth Q&A on Custom MCP Catalogs and Profiles—two powerful features that are transforming how organizations manage AI tooling with the Model Context Protocol (MCP). Whether you're an IT leader looking to standardize server usage or a developer eager to share configurations, this guide answers your most pressing questions. We'll explore how custom catalogs let you curate trusted MCP servers, and how profiles make it easy to build, run, and distribute your tools across teams. Let's dive in!

What Are Custom MCP Catalogs and Why Do They Matter?

Custom MCP Catalogs are curated collections of approved MCP servers that organizations can publish and distribute internally. Instead of each team member hunting for servers across the internet, teams get a single source of truth containing only vetted servers—including those built in-house. This centralization boosts trust, security, and efficiency. With catalogs, you can mix servers from Docker’s official catalog, community sources, and your own custom builds, all in one place. It’s a game-changer for enterprise adoption because it removes guesswork and ensures consistent, reliable AI tooling across projects.

How Do I Create a Custom MCP Catalog with Docker?

Creating a custom catalog involves a few clear steps. First, you need to package your MCP server as a Docker image and push it to a registry like Docker Hub. For example, you can build an image for a roll-dice server (a reference MCP server) and push it with a tag like roberthouse224/mcp-dice@latest. Then, you create a metadata file (e.g., mcp-dice.yaml) describing the server—its name, title, type, image location, and a brief description. Next, you compile a catalog that references both your own servers and ones from the Docker MCP Catalog. Finally, you share this catalog through Docker Desktop or the CLI, making it accessible to your entire team.

What Are MCP Profiles and How Do They Simplify Tool Management?

MCP Profiles are portable, named groupings of MCP servers that let individual developers define and share their tool configurations. Think of them as reusable blueprints: you can create a profile containing a specific set of MCP servers—say, a database connector and a weather API—then use that profile across different projects or share it with colleagues. Profiles solve real pain points by eliminating the need to manually configure servers each time. They also provide a foundation for future enhancements, such as role-based access or versioned profiles. For developers, this means less repetition and more consistency in their AI toolchain.

How Do MCP Profiles Support Team Collaboration?

Profiles are built for sharing. A developer can create a profile with their preferred MCP servers and export it as a simple configuration file. Team members can then import that profile into their own Docker Desktop environment with a single click. This ensures everyone uses the same, tested set of servers, reducing discrepancies and debugging time. Moreover, since profiles are platform-agnostic, they work across different operating systems and setups. As organizations scale, profiles enable best practices to spread naturally—senior developers can craft optimized profiles, and junior team members can adopt them instantly, accelerating onboarding and collaboration.

Can You Walk Me Through the Step-by-Step Process of Building a Custom Catalog?

Absolutely. Here’s a high-level walkthrough:

1. Create your MCP server – Build a standard MCP server (e.g., the roll-dice example from GitHub) that communicates over stdio and package it as a Docker image.
2. Push the image – Use Docker CLI to push your image to a registry like Docker Hub (e.g., docker push roberthouse224/mcp-dice).
3. Write a metadata file – Save a YAML file (e.g., mcp-dice.yaml) with fields like name, title, type, image, and description.
4. Assemble your catalog – Create a catalog file that references both your own server(s) and servers from the Docker MCP Catalog. You can list them as entries with pointers to their metadata or images.
5. Publish and distribute – Use Docker Desktop’s import feature or CLI commands to make the catalog available to your team. Once imported, team members can browse and use the approved servers instantly.

This approach gives you full control over server quality while leveraging community resources.

What Are the Key Benefits of Custom MCP Catalogs and Profiles for Enterprises?

Enterprises gain three major advantages: trust, control, and productivity. Trust comes from curating only verified servers, reducing the risk of malicious or unstable tools. Control is achieved by centrally managing which versions are allowed and who can publish catalogs. Productivity skyrockets because developers no longer waste time searching for servers or troubleshooting mismatched configurations. Additionally, profiles enable standardized tool sets across departments, making cross-functional projects smoother. As AI becomes integral to business processes, these features help scale MCP adoption without chaos, ensuring compliance and consistency.

How Do Custom Catalogs and Profiles Complement Each Other?

Think of catalogs as the “library” of approved servers and profiles as the “shelf” where you arrange your favorites. Catalogs give organizations a top-down way to define what’s available, while profiles empower individual developers to select, group, and share the servers they need. Together, they bridge governance and flexibility. A team can use a catalog to enforce security policies, yet each developer can create personal profiles for rapid prototyping. When sharing, profiles reference servers from the catalog, so all tools are pre-approved. This synergy makes enterprise MCP adoption both safe and agile.