MCP server · Engineering and operations

Postman MCP server

Postman in any MCP client, through Memtro: Postman does not publish this server. Memtro's Postman connector reads Postman through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Postman API platform: workspaces, collections, environments (names only), and monitors with their schedule and last run. When asked, comments on a collection or edits a comment, runs, creates, updates or deletes a monitor, creates a workspace or posts a workspace update, and duplicates or deletes a collection.

Reads

  • postman_workspacesPostman workspaces the key's user can see: id, name, type (personal, team, private, public, partner) and visibility.
  • postman_collectionsPostman collections, optionally in one workspace: id, uid (the unique ID other tools take), name, fork label and dates.
  • postman_environmentsPostman environments, optionally in one workspace: names, ids and dates only.
  • postman_monitorsPostman monitors: id, name, whether active, and the collection and environment they run.
  • postman_monitorOne Postman monitor: schedule (cron, timezone, next run), regions, and its last run's status, start and finish times and stats (runs, errors…

Acts, when you ask

These change something in Postman. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • postman_add_collection_commentAdd a comment to a Postman collection, as the key's user.
  • postman_update_collection_commentReplace the text of one comment on a Postman collection (the key's user must be its author).
  • postman_run_monitorRun a Postman monitor now, in the background.
  • postman_create_monitorCreate a Postman monitor that runs a collection on a schedule (POSIX cron and timezone), in the workspace given.
  • postman_update_monitorChange a Postman monitor: pause or resume it, rename it, reschedule it, or change its retries or regions.
  • postman_delete_monitorPermanently delete a Postman monitor and its schedule.
  • postman_create_workspaceCreate a Postman workspace: personal (only the key's user), private (invited members; Team and Enterprise plans) or team (everyone on the team).
  • postman_create_workspace_updatePost an update (improvement, new feature, bug fix, breaking change or announcement) to a Postman workspace.
  • postman_duplicate_collectionCopy a Postman collection into another workspace, optionally adding a suffix to its name.
  • postman_delete_collectionPermanently delete a Postman collection.

Connect it

First connect Postman on Dashboard → Connections, then add Memtro to your client once. The Postman tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Postman connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Did the nightly API monitor pass?
  • › Which Postman monitors are inactive?
  • › When does the checkout monitor run next?
  • › Add a comment to the Orders API collection saying the v2 endpoints are live.
  • › Run the checkout monitor now

Questions

Is this an official Postman MCP server?
No. It is Memtro's MCP server with Memtro's Postman connector behind it: the connector reads Postman through its API with the credentials you connect on Dashboard → Connections, and Postman publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Postman?
Only when you ask, and only what it has been granted: add a comment to a collection; edit a comment on a collection; run a monitor now (uses monitor run quota); create a scheduled monitor for a collection (uses monitor run quota on every run); pause, resume, rename or reschedule a monitor; delete a monitor (permanent); create a personal, private or team workspace; post an update to a workspace's watchers; duplicate a collection into another workspace; delete a collection (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time