Gateway customization
MintMCP's gateway is a curated, branded interface for your organization's AI tools—not just a proxy. You control what goes in your registry, how connectors are packaged for teams, and how they appear to users.
Custom registry
The MCP store is your organization's internal registry of approved AI tools. By default it's empty, and only admins can add to it.
You can populate your registry from four sources:
| Source | Description |
|---|---|
| Pre-vetted catalog | Browse and approve servers from MintMCP's curated list |
| Remote MCP | Connect external servers running in your own infrastructure |
| Hosted connector | Deploy open-source or custom MCP servers in MintMCP's managed runtime |
| Custom server | Bring your own code via the CLI and host it on MintMCP |
Together these let you build a registry tailored to your organization—mixing vendor integrations, internal APIs, and open-source tools under a single governed endpoint.
See Administration for the full process of adding servers to your registry.
Custom VMCP bundles
Rather than exposing raw connectors to users, you can bundle multiple MCPs into a single endpoint scoped to a team or use case. This is how most organizations structure their registry once they move past initial setup.
To create a bundle:
- Navigate to MCP store and click + Add an MCP to your registry
- Choose Create a role-based MCP bundle
- Name the bundle for its team or purpose—"Marketing Analytics", "DevOps Operations", "Sales Intelligence"
- Add the connectors the bundle should include
- Curate the tool set: enable only what the team needs, and rename or redescribe tools for clarity
- Set an access policy to restrict the bundle to the right group
Each bundle publishes as a single URL with centralized credentials, so users connect once instead of configuring each connector individually. Updates—adding a connector, disabling a tool, rotating credentials—propagate automatically to everyone using the bundle.
See Packaging VMCPs for teams for a full step-by-step example.
Logo customization
Each MCP server in your registry displays a logo so users can recognize connectors at a glance in the MCP store.
Connector logos provided by Logo.dev. If a connector maps to a recognized brand—Slack, Salesforce, GitHub—the logo appears automatically without any configuration. For connectors that don't have a logo.dev match, you can upload a custom logo. This applies to:
- Internal APIs wrapped as MCP servers
- VMCP bundles representing a team or department
- Open-source servers without a commercial brand
Logo guidelines:
- Square format, since the UI displays logos in a square crop
- SVG or PNG with a transparent background
- Legible at small sizes (the store renders logos at roughly 32–64px)
To set or replace a logo, open the connector's configuration in the MCP store.