Postman CLI for AI Agents

Framework Integration Gradient
Postman Logo
CLI Logo
divider

Introduction

CLIs are eating MCPs. The industry is converging on the very same idea. MCPs for all their merit can be token hungry, slow, and unreliable for complex tool chaining. However, coding agents have become incredibly good at working with CLIs, and in fact they are far more comfortable working with CLI tools than MCP.

With Composio's Universal CLI, your coding agents can talk to over 850+ SaaS applications. With Postman, agents can run the 'get users' request in postman, list all collections in your postman workspace, create a new environment variable in postman, and more — all without worrying about authentication.

This guide walks you through Composio Universal CLI and explains how you can connect it with coding agents like Claude Code, Codex, OpenCode, etc, for end-to-end Postman automation.

Also integrate Postman with

What is Universal CLI and why use it?

The idea behind building the universal CLI is to give agents a single command interface to interact with all your external applications. Here's what you'll get with it:

  • Agent-friendly: Coding agents like Claude Code, Codex, and OpenCode can use CLI tools natively — no MCP setup required.
  • Authentication handled: Connect once via OAuth or API Key, and all CLI commands work with your credentials automatically.
  • Tool discovery: Search, inspect, and execute 20,000+ tools across 850+ apps from one interface.
  • Trigger support: Use triggers to listen for events across your apps, powered by real-time webhooks or polling under the hood.
  • Type generation: Generate typed schemas for autocomplete and type safety in your projects.

Prerequisites

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login you'll be redirected to sign in page, finish the complete flow and you're all set.

Composio CLI authentication flow

Connecting Postman to Coding Agents via Universal CLI

Once it is installed, it's essentially done. Claude Code, Codex, OpenCode, OpenClaw, or any other agent will be able to access the CLI. A few steps to give agents access to your apps.

  1. Launch your Coding Agent — Claude Code, Codex, OpenCode, anything you prefer.
  2. Prompt it to "Authenticate with Postman"
  3. Complete the authentication and authorization flow and your Postman integration is all set.
  4. Start asking anything you want.

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.

Universal CLI Commands for Postman

You can also manually execute CLI commands to interact with your Postman.

Connect your Postman account

Link your Postman account and verify the connection:

bash
# Connect your Postman account (opens OAuth flow)
composio connected-accounts link postman

# Verify the connection
composio connected-accounts list --toolkits postman

Discover Postman tools

Search and inspect available Postman tools:

bash
# List all available Postman tools
composio tools list --toolkit postman

# Search for Postman tools by action
composio tools search "postman"

# Inspect a tool's input schema
composio tools info POSTMAN_CREATE_A_COLLECTION

Common Postman Actions

Create a CollectionTool to create a new Postman collection in a specific workspace or the default workspace

bash
composio tools execute POSTMAN_CREATE_A_COLLECTION \
  --collection "<object>"

Create a Collection CommentTool to create a comment on an API's collection

bash
composio tools execute POSTMAN_CREATE_A_COLLECTION_COMMENT \
  --body "This is a test comment on the API collection" \
  --api_id "4e01b242-d5c6-4bbe-90db-a550f2e723b4" \
  --collection_id "50304422-bc02b91a-1475-44ef-863f-ea795073bc41"

Create Collection from SchemaTool to create a collection from a schema and link it to an API with specified relations

bash
composio tools execute POSTMAN_CREATE_A_COLLECTION_FROM_A_SCHEMA \
  --name "Test Collection from Schema" \
  --api_id "4e01b242-d5c6-4bbe-90db-a550f2e723b4" \
  --schema_id "7a871867-f009-4aba-81c2-eaeea10c655b" \
  --api_version_id "a14d837d-6588-46cc-8079-98a705f0160c"

Create a FolderTool to create a folder in a Postman collection

bash
composio tools execute POSTMAN_CREATE_A_FOLDER \
  --name "Test Folder" \
  --collection_id "8a98fd90-d917-45b4-b856-14e67fb96d95"

Generate Type Definitions

Generate typed schemas for Postman tools to get autocomplete and type safety in your project:

bash
# Auto-detect language
composio generate --toolkits postman

# TypeScript
composio ts generate --toolkits postman

# Python
composio py generate --toolkits postman

Tips & Tricks

  • Always inspect a tool's input schema before executing: composio tools info <TOOL_NAME>
  • Pipe output with jq for better readability: composio tools execute TOOL_NAME -d '{}' | jq
  • Set COMPOSIO_API_KEY as an environment variable for CI/CD pipelines
  • Use composio dev logs tools to inspect execution logs and debug issues

Next Steps

  • Try asking your coding agent to perform various Postman operations
  • Explore cross-app workflows by connecting more toolkits
  • Set up triggers for real-time automation
  • Use composio generate for typed schemas in your projects

How to build Postman MCP Agent with another framework

FAQ

What is the Composio Universal CLI?

The Composio Universal CLI is a single command-line interface that lets coding agents and developers interact with 850+ SaaS applications. It handles authentication, tool discovery, action execution, and trigger setup — all from the terminal, without needing to configure MCP servers.

Which coding agents work with the Composio CLI?

Any coding agent that can run shell commands works with the Composio CLI — including Claude Code, Codex, OpenCode, OpenClaw, and others. Once the CLI is installed, agents automatically discover and use the composio commands to interact with Postman and other connected apps.

How is the CLI different from using an MCP server for Postman?

MCP servers require configuration and can be token-heavy for complex workflows. The CLI gives agents a direct, lightweight interface — no server setup needed. Agents simply call composio commands like any other shell tool. It's faster to set up, more reliable for multi-step tool chaining, and works natively with how coding agents already operate.

How safe is my Postman data when using the Composio CLI?

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. You can also bring your own OAuth credentials for full control.

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.