How to integrate Postman MCP with Claude Code

Manage your Postman directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Postman logoPostman
Api Key

Postman is an API platform for building, testing, and managing APIs with team collaboration tools. It's a go-to solution for streamlining API development and boosting productivity.

146 Tools

Introduction

Manage your Postman directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Postman with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Postman to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Postman MCP server, and what's possible with it?

The Postman MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Postman account. It provides structured and secure access so your agent can perform Postman operations on your behalf.

Connecting Postman via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Postman) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Postman account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['postman'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http postman-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Postman. This URL will be used to connect Claude Code to Postman.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Postman
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Postman MCP to Claude Code

bash
claude mcp add --transport http postman-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (postman-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Postman MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your postman-composio entry in the list
  • This confirms that Claude Code can now access Postman tools

If everything is wired up, you should see your postman-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Postman

The first time you try to use Postman tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Postman
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Postman authorization flow
  • Return to the terminal and start using Postman through Claude Code

Once authenticated, you can ask Claude Code to perform Postman operations in natural language. For example:

  • "Run the 'Get Users' request in Postman"
  • "List all collections in my Postman workspace"
  • "Create a new environment variable in Postman"

Complete Code

Here's the complete code to get you started with Postman and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['postman'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http postman-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Postman with Claude Code using Composio's MCP server. Now you can interact with Postman directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Postman operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Postman operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Postman action and event your agent gets out of the box.

Create a Collection

Tool to create a new Postman collection in a specific workspace or the default workspace.

Create a Collection Comment

Tool to create a comment on an API's collection.

Create Collection from Schema

Tool to create a collection from a schema and link it to an API with specified relations.

Create a Folder

Tool to create a folder in a Postman collection.

Create a Folder Comment

Tool to create a comment on a folder.

Create a Fork

Tool to create a fork from an existing collection into a workspace.

Create Environment Fork

Tool to create a fork from an existing environment into a workspace.

Create a Mock Server

Tool to create a new mock server in a Postman collection.

Create a Monitor

Tool to create a new monitor in a specific workspace to run a collection on a schedule.

Create an API

Tool to create a new API in Postman.

Create an API

Tool to create a new API in a Postman workspace.

Create an Environment

Tool to create a new environment in a Postman workspace.

Create a Pull Request

Tool to create a pull request for a forked collection into its parent collection.

Create Request in Collection

Tool to create a new request in a Postman collection.

Create a Request Comment

Tool to create a comment on a request.

Create a Response

Tool to create a request response in a Postman collection.

Create a Response Comment

Tool to create a comment on a response.

Create API Schema

Tool to create a schema for an API in Postman.

Create Mock Server Response

Tool to create a server response on a Postman mock server.

Create a Spec

Tool to create an API specification in Postman's Spec Hub.

Create Spec File

Tool to create a new file in an API specification.

Create a Webhook

Tool to create a webhook that triggers a collection with a custom payload.

Create a Workspace

Tool to create a new workspace in Postman.

Create Collection

Tool to create a new Postman collection with specified name and configuration.

Create Environment

Tool to create a new Postman environment with specified name and variables.

Create Mock Server

Tool to create a new mock server for a Postman collection.

Create Monitor

Tool to create a new monitor to run a collection on a schedule.

Create or Update a Schema File

Tool to create or update an API schema file in Postman.

Create API Version Relations

Tool to create new relations for an API version.

Create Webhook

Tool to create a new webhook for a Postman collection.

Delete a Collection

Tool to permanently delete a collection from Postman.

Delete a collection's comment

Tool to delete a comment from an API's collection.

Delete a Folder

Tool to delete a folder in a Postman collection.

Delete a Folder's Comment

Tool to delete a comment from a folder.

Delete an API

Tool to delete an API from Postman.

Delete an API's Comment

Tool to delete a comment from an API.

Delete an environment

Tool to delete an environment permanently in Postman.

Delete a Request's Comment

Tool to delete a comment from a request.

Delete a Response

Tool to delete a response in a Postman collection.

Delete a Response's Comment

Tool to delete a comment from a response.

Delete a Schema File

Tool to delete a file in an API schema.

Delete Mock Server Response

Tool to delete a mock server's server response.

Delete a Spec

Tool to delete an API specification from Postman.

Delete Spec File

Tool to delete a file from an API specification.

Delete a Workspace

Tool to delete a Postman workspace permanently.

Delete Monitor

Tool to delete a monitor by its ID.

Duplicate a Collection

Tool to create a duplicate of a collection in another workspace.

Fork Collection

Tool to create a fork of a collection in a specified workspace.

Generate Collection from Spec

Tool to generate a Postman collection from an OpenAPI 2.

Generate Spec from Collection

Tool to generate an API specification from a Postman collection.

Get Billing Account Details

Tool to retrieve Postman billing account details for the authenticated team.

Get Collection Comments

Tool to retrieve all comments left by users in an API's collection.

Get Collection's Forks

Tool to get all forks of a specific collection.

Get Collection Pull Requests

Tool to get information about a collection's pull requests including source and destination IDs, status, and URLs.

Get Collection Roles

Tool to get information about all roles in a collection.

Get Folder Information

Tool to retrieve information about a folder in a Postman collection.

Get Folder Comments

Tool to retrieve all comments left by users in a folder.

Get All API Releases

Tool to get all releases for a specific API version in Postman.

Get All APIs

Tool to get all APIs accessible to the authenticated user with optional workspace filtering.

Get All APIs in Workspace

Tool to get all APIs in a specific Postman workspace.

Get All Collections

Tool to get all collections accessible to the authenticated user with optional workspace filtering.

Get All Collections

Tool to get all collections accessible to the authenticated user.

Get All Environments

Tool to get all environments accessible to the authenticated user with optional workspace filtering.

Get All Forked Collections

Tool to retrieve all forked collections for the authenticated user.

Get All Groups

Tool to get all user groups in a Postman team.

Get All Linked Relations

Tool to retrieve all linked relations for a specific API version in Postman.

Get All Mock Servers

Tool to get all active mock servers accessible to the authenticated user.

Get All Monitors

Tool to get all monitors accessible to the authenticated user with optional workspace filtering.

Get All Workspace Roles

Tool to get information about all roles in a workspace based on the team's plan.

Get All API Specifications

Tool to get all API specifications in a workspace.

Get All Team Users

Tool to get information about all users on the Postman team.

Get All Test Relations

Tool to retrieve all test relations for a specific API version.

Get All API Versions

Tool to get all published versions of a specific API in Postman.

Get All Workspaces

Tool to get all workspaces accessible to the authenticated user with optional type filtering.

Get Monitor Information

Tool to retrieve information about a specific monitor in Postman.

Get API Information

Tool to retrieve information about a specific API in Postman.

Get API Comments

Tool to retrieve all comments left by users in an API.

Get API Version

Tool to get information about a specific API version in Postman.

Get an Environment

Tool to retrieve detailed information about a specific environment in Postman.

Get Environment Forks

Tool to retrieve all forked environments for a specific environment.

Get Request Information

Tool to retrieve information about a specific request in a Postman collection.

Get Request Comments

Tool to retrieve all comments left by users in a request.

Get Response Information

Tool to retrieve information about a saved response in a Postman collection.

Get Response Comments

Tool to retrieve all comments left by users in a response.

Get API Schema

Tool to retrieve information about an API schema from Postman.

Get API Specification

Tool to retrieve information about an API specification in Postman.

Get Spec File Contents

Tool to get the contents of an API specification's file.

Get Spec Definition

Tool to get the complete contents of an API specification's definition.

Get Specification Files

Tool to retrieve all files in an API specification from Postman.

Get Spec's Generated Collections

Tool to retrieve all collections generated from an API specification in Postman.

Get Async Collection Update Status

Tool to get the status of an asynchronous collection update task.

Get Team User

Tool to get information about a user on the Postman team.

Get Authenticated User

Tool to get information about the authenticated user.

Get Workspace Details

Tool to get detailed information about a specific workspace by its ID.

Get Workspace Activity Feed

Tool to get a workspace's activity feed showing who added or removed collections, environments, or elements, and users joining or leaving.

Get Workspace Roles

Tool to get the roles of users, user groups, and partners in a workspace.

Get Collection Access Keys

Tool to retrieve all personal and team collection access keys for the authenticated user.

Get Contract Test Relations

Tool to retrieve contract test relations for a specific API version.

Get documentation relations

Tool to get documentation relations for a specific API version.

Get Duplication Task Status

Tool to get the status of a collection duplication task.

Get Environment Relations

Tool to get environment relations for a specific API version.

Get Generated Specification

Tool to retrieve the API specification generated for a Postman collection.

Get Workspace Global Variables

Tool to get a workspace's global variables.

Get Integration Test Relations

Tool to get integration test relations for a specific API version.

Get Resource Types

Tool to get all resource types supported by Postman's SCIM API.

Get Schema File Contents

Tool to get the contents of an API schema file at a specified path.

Get Schema Files

Tool to retrieve files in an API schema from Postman.

Get Service Provider Configuration

Tool to get Postman's SCIM API service provider configuration information.

Get Source Collection Status

Tool to check whether there is a change between a forked collection and its parent (source) collection.

Get Test Suite Relations

Tool to get test suite relations for a specific API version.

Get Unclassified Relations

Tool to get unclassified relations for an API version in Postman.

Import OpenAPI Definition

Tool to import an OpenAPI definition into Postman as a new collection.

Import OpenAPI Specification

Tool to import an OpenAPI specification into Postman as a new collection.

List Account Invoices

Tool to get all invoices for a Postman billing account filtered by status.

Merge a Fork

Tool to merge a forked collection back into its parent collection.

Merge a forked environment

Tool to merge a forked environment back into its parent environment.

Publish a Mock Server

Tool to publish a mock server in Postman.

Pull Source Changes into Fork

Tool to pull changes from a parent (source) collection into a forked collection.

Replace an Environment's Data

Tool to completely replace an environment's data with new variables and values.

Replace Collection Data Asynchronously

Tool to replace the entire contents of a collection asynchronously.

Resolve a Comment Thread

Tool to resolve a comment thread and any associated replies.

Review a Pull Request

Tool to update the review status of a pull request by approving, declining, or unapproving it.

Run a Monitor

Tool to trigger an immediate run of a monitor and retrieve its execution results.

Sync Collection with API Schema

Tool to sync a collection attached to an API with the API schema.

Sync Collection with Specification

Tool to sync a collection generated from an API specification.

Sync Spec with Collection

Tool to sync an API specification with a linked collection.

Transfer Folders

Tool to copy or move folders into a collection or folder.

Transform Collection to OpenAPI

Tool to transform an existing Postman Collection into a stringified OpenAPI 3.

Update a Folder

Tool to update a folder in a Postman collection.

Update a Folder's Comment

Tool to update a comment on a folder.

Update a Mock Server

Tool to update an existing mock server.

Update a Monitor

Tool to update an existing monitor in Postman.

Update an API

Tool to update an existing API in Postman.

Update an API's Comment

Tool to update a comment on an API.

Update an Environment

Tool to update specific environment properties using JSON Patch operations (RFC 6902).

Update a Pull Request

Tool to update an open pull request in Postman.

Update Request in Collection

Tool to update a request in a Postman collection.

Update a Request's Comment

Tool to update a comment on a request.

Update a Response

Tool to update a response in a Postman collection.

Update a Response's Comment

Tool to update a comment on a response.

Update a Server Response

Tool to update a mock server's server response.

Update Spec File

Tool to update an API specification file's content.

Update Spec Properties

Tool to update an API specification's properties such as its name.

Update a Workspace

Tool to update an existing workspace in Postman.

Update Workspace Global Variables

Tool to update and replace a workspace's global variables.

Update Collection Properties

Tool to update specific collection properties like name, description, authentication, variables, or events.

FAQ

Frequently asked questions

With a standalone Postman MCP server, the agents and LLMs can only access a fixed set of Postman tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Postman and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Postman tools.

Yes, absolutely. You can configure which Postman scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Postman data and credentials are handled as safely as possible.

Start with Postman.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Postman tool your agent needs.Free to start.

Start building