Postman MCP Generator

Provides an MCP-compatible server with automatically generated tools for selected Postman API requests.

javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "m-shirt-paytal-mcp": {
      "command": "node",
      "args": [
        "mcpServer.js"
      ],
      "env": {
        "ACME_API_KEY": "YOUR_ACME_API_KEY",
        "WIDGETS_API_KEY": "YOUR_WIDGETS_API_KEY"
      }
    }
  }
}

You have a local MCP server that exposes your Postman API requests as MCP-compatible tools. Runable in stdio mode for CLI integration or with optional flags to enable streaming HTTP or SSE endpoints, it lets you connect an MCP client and execute your selected tools in an automated or conversational workflow.

How to use

Set up an MCP client to connect to your local server. Start the server in stdio mode for CLI or embedding into other tools, or run it with flags to enable additional endpoints when needed. Once the server is running, you’ll see a list of your generated tools in the client. Use those tools to perform authenticated API requests from your workflow without writing custom HTTP calls. Each tool corresponds to a specific Postman API request you selected during generation. Begin a chat or automation session with your MCP client and invoke the tools you need to retrieve data, perform actions, or test integrations.

How to install

Prerequisites you need before starting: Node.js v18+ (v20+ recommended) and npm. If you run with an older Node version, fetch may not be available by default and you may need to install node-fetch and alias it as fetch in your tool files.

Install dependencies for the project. Run from your project root:

npm install

Create or update environment variables for the tools you generated. In your project, provide values for each workspace API key as shown by the example placeholders in the .env file. Typical placeholders look like this:

ACME_API_KEY=
WIDGETS_API_KEY=

Start the MCP server in standard input/output mode. This is the baseline runtime command:

node mcpServer.js

Optional: run with Streamable HTTP enabled to expose a /mcp endpoint for streaming HTTP clients:

node mcpServer.js --streamable-http

Optional: run with Server-Sent Events enabled to expose /sse and /messages endpoints for real-time updates:

node mcpServer.js --sse

Additional content

Environment management: Keep API keys in a dedicated .env file and ensure your MCP client can access them through the environment when invoking tools. If you customize the generated tools to use a different authentication method, adjust the environment access accordingly.

Testing the server locally: You can validate that the server loads and your tools are discoverable by running the server and listing available tools in your MCP client, then invoking each tool to verify the corresponding API requests succeed.

Available tools

login

Tool to authenticate a user by providing an email and password; used to access protected endpoints.

list_all_customers

Retrieves a list of useful items or customers from a workspace as part of the examples in the generated tools.