Promote your MCP server on the Postman API Network

The Postman API Network is where millions of developers discover, test, and integrate APIs. Publishing your work on the Postman API Network is a powerful way to get new customers and drive deeper adoption from your existing user base. As the industry shifts towards AI-driven applications, developers are actively seeking new ways for agents and models to interact programmatically with services.

You’ve already built an MCP server to give AI agents a dedicated entry point to your services. The next step is to get it in front of the developers who need it. Publishing your server on the Postman API Network makes it available to developers building AI-powered features, allowing them to discover, test, and integrate with your MCP server, within Postman.

This topic guides you through the steps to publish your MCP server and feature it in Postman's official MCP Catalog, connecting your work with the world's largest and most active API community.

Become a publisher

The first step to publishing on the Postman API Network is sharing your public APIs. Before adding an MCP server, your team needs a complete public profile and at least one public workspace that contains your well-documented API collections.

The goal is to become a verified publisher, which builds consumer trust and awards your team a blue "verified" badge. This verification is critical when it comes to MCP servers. Because AI agents execute actions based on the tools your server provides, developers need absolute confidence that they're integrating with the official, authoritative source.

To learn more about setting up your public profile, creating public workspaces, and preparing for verification, see Showcase your public APIs on the Postman API Network.

Once you are an established publisher sharing your APIs, you'll be ready to add your MCP server to your public workspace.

Build your MCP server collection

Once your team is established as a publisher, you're ready to add your MCP server to a new collection. To build out your MCP collection, do the following:

1. Create a new collection within your workspace and give it a clear name, for example, "My AI Service MCP Server".

2. Add a detailed description to your collection. The description must explain primary use cases for your MCP server and how to get started. Be sure to include any authentication or setup instructions.

3. Add an MCP request for each MCP server configuration. Postman supports different types of MCP servers. You need to add one or more requests to your collection that lets users to interact with your server.

   • For local servers: If one or more of your MCP servers are run locally using a command-line tool, you can add a STDIO request for each server that includes the necessary command and arguments, for example npx -y @mycompany/mycompany-mcp-server. You must include all necessary environment variables.
   • For remote servers: If your server can be reached using HTTP or SSE, add a request with the requisite URL and assign the HTTP request type. You must include all necessary environment variables.

   

Learn more about configuring MCP requests.

Make a workspace update announcing your MCP server

When your collection is ready, announce it to the community using a workspace update. These updates appear on your public workspace and in the Postman API Network's news feed, ensuring maximum visibility.

Add your MCP server to the Postman MCP Catalog

The official Postman MCP Catalog is a curated list of high-quality, official MCP servers. The best way to have your server included is to follow the steps to become a publisher and create a complete, public MCP collection in your own workspace.

Once your public MCP collection is ready, email Postman at api-network@postman.com. The team will review your submission and, upon approval, fork it into the official catalog.

If you're not a publisher yet, but would like to suggest an MCP server for the catalog, reach out to our team at the same email address. Please include a link to your official documentation and any necessary configuration details for our team to review ahead of adding your server to the catalog.