# How to connect Postman to OpenClaw (paste one key, 126 tools) > Connect Postman to OpenClaw with ClawLink: paste your Postman key once and 126 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/postman The usual route to Postman access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Postman setup: install one ClawHub skill, connect Postman in the browser, and OpenClaw can call real Postman actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/postman ## Setup It takes three steps to connect OpenClaw to Postman. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Postman** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect postman # connect Postman (browser OAuth) npx -y @useclawlink/cli actions postman # list available actions npx -y @useclawlink/cli run postman --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Postman in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Postman API key once. Verify the connection by asking OpenClaw: > Create it in Postman for me, then confirm the important fields before you finish. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Postman is connected in the dashboard, that agent calls the same 126 Postman tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Postman MCP for OpenClaw Looking for a Postman MCP server for OpenClaw? ClawLink connects Postman to OpenClaw and exposes 126 Postman tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Postman integration](https://claw-link.dev/hermes/postman) works the same way. ## What the OpenClaw Postman integration can do 126 Postman tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 126. ### 30 of 126 Postman tools for OpenClaw | Tool | What it does | |---|---| | **Create a collection** `postman_create_a_collection` | Create a new Postman collection in a specific workspace or the default workspace | | **Create a collection comment** `postman_create_a_collection_comment` | Create a comment on an API's collection | | **Create a folder** `postman_create_a_folder` | Create a folder in a Postman collection | | **Create a folder comment** `postman_create_a_folder_comment` | Create a comment on a folder | | **Get a collections comments** `postman_get_a_collections_comments` | Retrieve all comments left by users in an API's collection | | **Get a collections forks** `postman_get_a_collections_forks` | Get all forks of a specific collection | | **Get a collections pull requests** `postman_get_a_collections_pull_requests` | Get information about a collection's pull requests including source and destination IDs, status, and URLs | | **Get a collections roles** `postman_get_a_collections_roles` | Get information about all roles in a collection | | **Get a folder** `postman_get_a_folder` | Retrieve information about a folder in a Postman collection | | **Get a folders comments** `postman_get_a_folders_comments` | Retrieve all comments left by users in a folder | | **Get a monitor** `postman_get_a_monitor` | Retrieve information about a specific monitor in Postman | | **Get a request** `postman_get_a_request` | Retrieve information about a specific request in a Postman collection | | **Get a requests comments** `postman_get_a_requests_comments` | Retrieve all comments left by users in a request | | **Get a response** `postman_get_a_response` | Retrieve information about a saved response in a Postman collection | | **Get a responses comments** `postman_get_a_responses_comments` | Retrieve all comments left by users in a response | | **Get a schema** `postman_get_a_schema` | Retrieve information about an API schema from Postman | | **Get a spec** `postman_get_a_spec` | Retrieve information about an API specification in Postman | | **Get a spec file** `postman_get_a_spec_file` | Get the contents of an API specification's file | | **Get a specs definition** `postman_get_a_specs_definition` | Get the complete contents of an API specification's definition | | **Get a specs files** `postman_get_a_specs_files` | Retrieve all files in an API specification from Postman | | **Get a specs generated collections** `postman_get_a_specs_generated_collections` | Retrieve all collections generated from an API specification in Postman | | **Get a team user** `postman_get_a_team_user` | Get information about a user on the Postman team | | **Get a workspace** `postman_get_a_workspace` | Get detailed information about a specific workspace by its ID | | **Get a workspaces activity feed** `postman_get_a_workspaces_activity_feed` | Get a workspace's activity feed showing who added or removed collections, environments, or | | **Get a workspaces roles** `postman_get_a_workspaces_roles` | Get the roles of users, user groups, and partners in a workspace | | **Get accounts** `postman_get_accounts` | Retrieve Postman billing account details for the authenticated team | | **Get all apis** `postman_get_all_apis` | Get all APIs accessible to the authenticated user with optional workspace filtering | | **Get all collections2** `postman_get_all_collections2` | Get all collections accessible to the authenticated user | | **Get all environments** `postman_get_all_environments` | Get all environments accessible to the authenticated user with optional workspace filtering | | **Get all forked collections** `postman_get_all_forked_collections` | Retrieve all forked collections for the authenticated user | ## Example prompts **Create A Collection** > Create it in Postman for me, then confirm the important fields before you finish. **Create A Collection Comment** > Create it in Postman for me, then confirm the important fields before you finish. **Create A Folder** > Create it in Postman for me, then confirm the important fields before you finish. **Create A Folder Comment** > Create it in Postman for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Postman working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Postman API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Postman account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Postman. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Postman actions to the runtime in a format your agent can reliably use. | 126 tools for Postman are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Postman to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Postman in the browser, and the 126 tools above work from chat. There is no SDK and no config file, and the Postman key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Postman skill but can't call the tools The ClawHub skill teaches OpenClaw about Postman, but the calls run through the ClawLink plugin and your connected account. Make sure Postman is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Postman from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Postman tools Postman tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Postman call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Postman returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Postman has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Postman integration? Yes. ClawLink is the fastest way to connect OpenClaw to Postman: link your Postman account once in the browser and OpenClaw can call the Postman API through 126 ready-made tools — no custom code or token handling. ### How do I add Postman to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Postman skill from ClawHub, then you click Connect in the dashboard to authorize Postman. OpenClaw calls the tools from the next message — no config files, and the Postman key you paste is stored server-side instead of in your environment. ### How long does it take to connect Postman to OpenClaw? About two minutes. Sign in, click Connect next to Postman in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Postman up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Postman working from chat. ### OpenClaw installed the Postman skill but can't call the tools The ClawHub skill teaches OpenClaw about Postman, but the calls run through the ClawLink plugin and your connected account. Make sure Postman is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.