How to integrate Postman MCP with Claude Code

GET STARTED FOR FREE
Framework Integration Gradient
Postman Logo
Claude Code Logo
divider

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 Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Postman to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Postman.

Rube connected successfully

Supported Tools & Triggers

Tools
Create a CollectionTool to create a new Postman collection in a specific workspace or the default workspace.
Create a Collection CommentTool to create a comment on an API's collection.
Create Collection from SchemaTool to create a collection from a schema and link it to an API with specified relations.
Create a FolderTool to create a folder in a Postman collection.
Create a Folder CommentTool to create a comment on a folder.
Create a ForkTool to create a fork from an existing collection into a workspace.
Create Environment ForkTool to create a fork from an existing environment into a workspace.
Create a Mock ServerTool to create a new mock server in a Postman collection.
Create a MonitorTool to create a new monitor in a specific workspace to run a collection on a schedule.
Create an APITool to create a new API in Postman.
Create an APITool to create a new API in a Postman workspace.
Create an EnvironmentTool to create a new environment in a Postman workspace.
Create a Pull RequestTool to create a pull request for a forked collection into its parent collection.
Create Request in CollectionTool to create a new request in a Postman collection.
Create a Request CommentTool to create a comment on a request.
Create a ResponseTool to create a request response in a Postman collection.
Create a Response CommentTool to create a comment on a response.
Create API SchemaTool to create a schema for an API in Postman.
Create Mock Server ResponseTool to create a server response on a Postman mock server.
Create a SpecTool to create an API specification in Postman's Spec Hub.
Create Spec FileTool to create a new file in an API specification.
Create a WebhookTool to create a webhook that triggers a collection with a custom payload.
Create a WorkspaceTool to create a new workspace in Postman.
Create CollectionTool to create a new Postman collection with specified name and configuration.
Create EnvironmentTool to create a new Postman environment with specified name and variables.
Create Mock ServerTool to create a new mock server for a Postman collection.
Create MonitorTool to create a new monitor to run a collection on a schedule.
Create or Update a Schema FileTool to create or update an API schema file in Postman.
Create API Version RelationsTool to create new relations for an API version.
Create WebhookTool to create a new webhook for a Postman collection.
Delete a CollectionTool to permanently delete a collection from Postman.
Delete a collection's commentTool to delete a comment from an API's collection.
Delete a FolderTool to delete a folder in a Postman collection.
Delete a Folder's CommentTool to delete a comment from a folder.
Delete an APITool to delete an API from Postman.
Delete an API's CommentTool to delete a comment from an API.
Delete an environmentTool to delete an environment permanently in Postman.
Delete a Request's CommentTool to delete a comment from a request.
Delete a ResponseTool to delete a response in a Postman collection.
Delete a Response's CommentTool to delete a comment from a response.
Delete a Schema FileTool to delete a file in an API schema.
Delete Mock Server ResponseTool to delete a mock server's server response.
Delete a SpecTool to delete an API specification from Postman.
Delete Spec FileTool to delete a file from an API specification.
Delete a WorkspaceTool to delete a Postman workspace permanently.
Delete MonitorTool to delete a monitor by its ID.
Duplicate a CollectionTool to create a duplicate of a collection in another workspace.
Fork CollectionTool to create a fork of a collection in a specified workspace.
Generate Collection from SpecTool to generate a Postman collection from an OpenAPI 2.
Generate Spec from CollectionTool to generate an API specification from a Postman collection.
Get Billing Account DetailsTool to retrieve Postman billing account details for the authenticated team.
Get Collection CommentsTool to retrieve all comments left by users in an API's collection.
Get Collection's ForksTool to get all forks of a specific collection.
Get Collection Pull RequestsTool to get information about a collection's pull requests including source and destination IDs, status, and URLs.
Get Collection RolesTool to get information about all roles in a collection.
Get Folder InformationTool to retrieve information about a folder in a Postman collection.
Get Folder CommentsTool to retrieve all comments left by users in a folder.
Get All API ReleasesTool to get all releases for a specific API version in Postman.
Get All APIsTool to get all APIs accessible to the authenticated user with optional workspace filtering.
Get All APIs in WorkspaceTool to get all APIs in a specific Postman workspace.
Get All CollectionsTool to get all collections accessible to the authenticated user with optional workspace filtering.
Get All CollectionsTool to get all collections accessible to the authenticated user.
Get All EnvironmentsTool to get all environments accessible to the authenticated user with optional workspace filtering.
Get All Forked CollectionsTool to retrieve all forked collections for the authenticated user.
Get All GroupsTool to get all user groups in a Postman team.
Get All Linked RelationsTool to retrieve all linked relations for a specific API version in Postman.
Get All Mock ServersTool to get all active mock servers accessible to the authenticated user.
Get All MonitorsTool to get all monitors accessible to the authenticated user with optional workspace filtering.
Get All Workspace RolesTool to get information about all roles in a workspace based on the team's plan.
Get All API SpecificationsTool to get all API specifications in a workspace.
Get All Team UsersTool to get information about all users on the Postman team.
Get All Test RelationsTool to retrieve all test relations for a specific API version.
Get All API VersionsTool to get all published versions of a specific API in Postman.
Get All WorkspacesTool to get all workspaces accessible to the authenticated user with optional type filtering.
Get Monitor InformationTool to retrieve information about a specific monitor in Postman.
Get API InformationTool to retrieve information about a specific API in Postman.
Get API CommentsTool to retrieve all comments left by users in an API.
Get API VersionTool to get information about a specific API version in Postman.
Get an EnvironmentTool to retrieve detailed information about a specific environment in Postman.
Get Environment ForksTool to retrieve all forked environments for a specific environment.
Get Request InformationTool to retrieve information about a specific request in a Postman collection.
Get Request CommentsTool to retrieve all comments left by users in a request.
Get Response InformationTool to retrieve information about a saved response in a Postman collection.
Get Response CommentsTool to retrieve all comments left by users in a response.
Get API SchemaTool to retrieve information about an API schema from Postman.
Get API SpecificationTool to retrieve information about an API specification in Postman.
Get Spec File ContentsTool to get the contents of an API specification's file.
Get Spec DefinitionTool to get the complete contents of an API specification's definition.
Get Specification FilesTool to retrieve all files in an API specification from Postman.
Get Spec's Generated CollectionsTool to retrieve all collections generated from an API specification in Postman.
Get Async Collection Update StatusTool to get the status of an asynchronous collection update task.
Get Team UserTool to get information about a user on the Postman team.
Get Authenticated UserTool to get information about the authenticated user.
Get Workspace DetailsTool to get detailed information about a specific workspace by its ID.
Get Workspace Activity FeedTool to get a workspace's activity feed showing who added or removed collections, environments, or elements, and users joining or leaving.
Get Workspace RolesTool to get the roles of users, user groups, and partners in a workspace.
Get Collection Access KeysTool to retrieve all personal and team collection access keys for the authenticated user.
Get Contract Test RelationsTool to retrieve contract test relations for a specific API version.
Get documentation relationsTool to get documentation relations for a specific API version.
Get Duplication Task StatusTool to get the status of a collection duplication task.
Get Environment RelationsTool to get environment relations for a specific API version.
Get Generated SpecificationTool to retrieve the API specification generated for a Postman collection.
Get Workspace Global VariablesTool to get a workspace's global variables.
Get Integration Test RelationsTool to get integration test relations for a specific API version.
Get Resource TypesTool to get all resource types supported by Postman's SCIM API.
Get Schema File ContentsTool to get the contents of an API schema file at a specified path.
Get Schema FilesTool to retrieve files in an API schema from Postman.
Get Service Provider ConfigurationTool to get Postman's SCIM API service provider configuration information.
Get Source Collection StatusTool to check whether there is a change between a forked collection and its parent (source) collection.
Get Test Suite RelationsTool to get test suite relations for a specific API version.
Get Unclassified RelationsTool to get unclassified relations for an API version in Postman.
Import OpenAPI DefinitionTool to import an OpenAPI definition into Postman as a new collection.
Import OpenAPI SpecificationTool to import an OpenAPI specification into Postman as a new collection.
List Account InvoicesTool to get all invoices for a Postman billing account filtered by status.
Merge a ForkTool to merge a forked collection back into its parent collection.
Merge a forked environmentTool to merge a forked environment back into its parent environment.
Publish a Mock ServerTool to publish a mock server in Postman.
Pull Source Changes into ForkTool to pull changes from a parent (source) collection into a forked collection.
Replace an Environment's DataTool to completely replace an environment's data with new variables and values.
Replace Collection Data AsynchronouslyTool to replace the entire contents of a collection asynchronously.
Resolve a Comment ThreadTool to resolve a comment thread and any associated replies.
Review a Pull RequestTool to update the review status of a pull request by approving, declining, or unapproving it.
Run a MonitorTool to trigger an immediate run of a monitor and retrieve its execution results.
Sync Collection with API SchemaTool to sync a collection attached to an API with the API schema.
Sync Collection with SpecificationTool to sync a collection generated from an API specification.
Sync Spec with CollectionTool to sync an API specification with a linked collection.
Transfer FoldersTool to copy or move folders into a collection or folder.
Transform Collection to OpenAPITool to transform an existing Postman Collection into a stringified OpenAPI 3.
Update a FolderTool to update a folder in a Postman collection.
Update a Folder's CommentTool to update a comment on a folder.
Update a Mock ServerTool to update an existing mock server.
Update a MonitorTool to update an existing monitor in Postman.
Update an APITool to update an existing API in Postman.
Update an API's CommentTool to update a comment on an API.
Update an EnvironmentTool to update specific environment properties using JSON Patch operations (RFC 6902).
Update a Pull RequestTool to update an open pull request in Postman.
Update Request in CollectionTool to update a request in a Postman collection.
Update a Request's CommentTool to update a comment on a request.
Update a ResponseTool to update a response in a Postman collection.
Update a Response's CommentTool to update a comment on a response.
Update a Server ResponseTool to update a mock server's server response.
Update Spec FileTool to update an API specification file's content.
Update Spec PropertiesTool to update an API specification's properties such as its name.
Update a WorkspaceTool to update an existing workspace in Postman.
Update Workspace Global VariablesTool to update and replace a workspace's global variables.
Update Collection PropertiesTool to update specific collection properties like name, description, authentication, variables, or events.

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 Tool Router

Tool Router 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 Tool Router works

The Tool Router 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

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

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:

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

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)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["postman"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http postman-composio "{COMPOSIO_MCP_URL}" --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

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python 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

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.

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

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 os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["postman"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http postman-composio "{COMPOSIO_MCP_URL}" --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.

How to build Postman MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Postman MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Postman MCP with Claude Agent SDK

Google ADK

Google ADK

Use Postman MCP with Google ADK

LangChain

LangChain

Use Postman MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Postman MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Postman MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Postman MCP with LlamaIndex

CrewAI

CrewAI

Use Postman MCP with CrewAI

Codex

Codex

Use Postman MCP with Codex

FAQ

What are the differences in Tool Router MCP and Postman MCP?

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.

Can I use Tool Router MCP with Claude Code?

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.

Can I manage the permissions and scopes for Postman while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free