You built the app. Now you need to list it in the app store — and plug it into your other devices. This module is about portability: making your MCP server useful beyond the Postman tab it was born in.
Export MCP server configs for Claude Desktop, Cursor, and VS Code and know exactly where to paste them
Add your server to Agent Mode — closing the loop between building a server and using it inside Postman
Understand the pathway to publishing on the Postman API Network and why verified trust signals matter more for MCP than for regular APIs
Think of an MCP host like a smart home hub — a Philips Hue bridge, say. The bulbs (your tools) don't magically appear in the app just because they exist. You have to register them by telling the hub the right address. Claude Desktop, Cursor, VS Code with Copilot all work the same way: each one has a config file waiting for your server's command or URL. Once it's in there, the host discovers your tools automatically on startup.
Postman generates the exact config block you need. Pick your host below to see it — annotated so you know what every field actually means.
Here's the callback to the prerequisite course: Agent Mode is an MCP host. It speaks MCP natively. Which means the server you just built in the previous module can talk directly to your Postman agent — no config file editing, no path copying, no restarting anything.
The flow is four steps. Walk through them below to see exactly how it works.
This isn't a requirement — it's an opportunity. The Postman MCP Catalog is where millions of developers discover servers to connect their agents to. If you built something genuinely useful, this is how other people's agents find it.
The checklist below covers everything you need to get your server into the catalog. Check items off as you go. All four required items must be done before you submit — but the fifth one is the step most people forget, and it's the one that actually drives discovery.
The video below walks through exporting a config for one MCP host, pasting it in, restarting the host, and sending a real request from outside Postman. Then a peek at what a well-published server looks like in the catalog.
Export your server's configuration for whichever MCP host you use most (or most want to try). Paste it in, restart the host, and send it one real request from outside Postman.
That moment when an external tool calls something you built in Postman — when the response comes back and it worked — that's the payoff. Everything else in this course was setup for that.