Query Context Graph with an MCP client

Postman Context Graph (also known as Agent Context) is reachable as a toolset on the Postman MCP Server, alongside the existing Minimal, Code, Full, and Learn toolsets. The Context Graph toolset exposes two tools, submitContextGraphAsk and getContextGraphAsk, so an agent connected through Claude Code, Cursor, VS Code, or any other MCP client can ask questions like “what depends on billing-api?” without checking each collection.

To learn how to connect an MCP client to the Postman MCP server, see Set up a remote Postman MCP server and Set up a local Postman MCP server. Connecting to Context Graph works the same way as any other toolset, only the endpoint or flag changes.

Prerequisites

Context Graph enabled for your team. Check with your Postman admin.
A Postman API key, unless you’re connecting to the US remote server with OAuth.
Decision to connect remotely (recommended) or locally. Remote is hosted by Postman over HTTPS with no local process. Local runs on your machine over STDIO. Both expose the same two tools.

Connect to the Context Graph toolset

Add the Context Graph endpoint or flag wherever you’d normally point at Minimal, Code, Full, or Learn toolsets. The table below shows the remote endpoints and the local flag:

Mode	Region	Address
Remote	US	`https://mcp.postman.com/context-graph`
Remote	EU	`https://mcp.eu.postman.com/context-graph`
Local	—	`npx @postman/postman-mcp-server --context-graph`

The US remote endpoint supports OAuth or an API key as a Bearer token. The EU remote endpoint and the local server support API key authentication only. Any client config you’d write for another toolset works by changing just that URL or flag.

Verify your connection

Restart or reload your MCP host, then confirm it lists a server with two tools (submitContextGraphAsk, getContextGraphAsk). Try a prompt like this:

What depends on billing-api?

If your agent calls submitContextGraphAsk, then polls getContextGraphAsk and comes back with an answer, you’re connected.

Each ask counts against the team’s Context Graph quota, so ask one well-formed question rather than retrying variations.

This mirrors the Context Graph API’s POST .../asks → GET .../asks/{askId} shape. It has the same submit-then-poll pattern, just as MCP tools instead of HTTP calls.

Telemetry

The telemetry follows the same policy as the rest of the Postman MCP server. Remote servers collect anonymous usage telemetry by default. The local servers don’t collect telemetry, unless you set POSTMAN_MCP_TELEMETRY=true in the server’s environment.