Skip to main content
Back to the Postman MCP server

MCP Gateway · OpenCode

Postman icon

Connect Postman to OpenCode

OpenCode users can design an API in Postman from the terminal: draft the spec, generate a collection from it and fork it for a feature branch. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it, and reports token and cost totals per turn.

Category
Developer tools
Tools
113
Authentication
API key
OpenCode
Terminal

Behind the MCP Gateway

Run Postman MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Postman call inspected and logged.

Deploy on MCP Gateway

Set up

Add Postman to OpenCode in 4 steps

  1. 01

    Add Postman from the catalog

    An admin finds Postman in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Postman authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Postman

    Give teams the mcp:connect scope on the Postman server through team access or a role. OpenCode connects to the Postman server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Postman from OpenCode

    The first time OpenCode connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Postman's tools appear in OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Postman

Draft a new spec in Spec Hub

Describe the endpoints you plan to build and let OpenCode create the specification and its files in Postman, then generate a collection to exercise them.

createSpeccreateSpecFilegenerateCollection

Fork a collection for a branch

Work on breaking changes in a fork of the team collection, then check whether the parent has moved and pull its changes in before you open a pull request.

createCollectionForkgetSourceCollectionStatuspullCollectionChanges

Add a monitor for a new endpoint

When an endpoint is ready, OpenCode creates a Postman monitor for it so failures show up on a schedule rather than in a customer report.

createMonitor

Tools

113 tools

Each Postman tool can be allowed or denied per team and role at the MCP Gateway before OpenCode sees it.

addWorkspaceToPrivateNetwork

Publishes a workspace to your team's Private API Network.

createCollection

Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).

createCollectionComment

Creates a comment on a collection. To create a reply on an existing comment, include the \threadId\ property in the request body.

createCollectionFolder

Creates a folder in a collection. For a complete list of properties, refer to the Folder entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).

createCollectionFork

Creates a [fork](https://learning.postman.com/docs/collaborating-in-postman/version-control/#creating-a-fork) from an existing collection into a workspace.

createCollectionRequest

Creates a request in a collection. For a complete list of properties, refer to the Request entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).

See all 113 tools

Control

What Speakeasy can see and stop in OpenCode

The gateway covers every client the same way. The rest depends on what OpenCode exposes to Speakeasy.

Tool logs

Gateway

Every Postman call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Postman tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Postman can reject a tool request before it reaches the server, or withhold a result from OpenCode. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

How does OpenCode get the Postman server?
OpenCode doesn't receive MCP servers from plugins. Copy the server's URL from its hosted install page in Speakeasy and add it to the mcp block of your OpenCode config as a remote server.
Can tool output from Postman be blocked in OpenCode?
Tool output is blocked at the gateway rather than in OpenCode's hooks. Prompts and tool calls are checked by the OpenCode plugin before they run.
How do OpenCode users get Postman?
An admin adds Postman from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Postman tools their access allows.
Are Postman calls from OpenCode logged?
Yes. Postman calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Postman in other clients

AI everywhere.

Control here.