Bring Api Testing
to VS Code Copilot
Learn how to connect Postman to VS Code Copilot and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Postman MCP Server?
Connect your Postman organizational account to any AI agent and take full control of your API development and documentation workflows through natural conversation.
What you can do
- Workspaces & Collections — List all personal and team workspaces and fetch API collections directly from the Postman cloud
- Request Management — Query all recorded requests (both headers and body) from any target collection using its unique ID
- Deep Environment Inspection — Fetch complete variable sets, values, and precise configurations for specific environments
- API Documentation — List API definitions and schemas to understand and integrate with internal or external services
- Infrastructure Monitoring — Retrieve the status of scheduled monitors and mock servers to ensure service availability
How it works
1. Subscribe to this server
2. Enter your Postman API Key from your account settings
3. Start managing your API resources from Claude, Cursor, or any MCP-compatible client
No more wrestling with complex UI tabs to find documentation or variable values. Your AI acts as a dedicated API architect or technical lead assistant.
Who is this for?
- Software Engineers — instantly retrieve request details, check environment variables, and inspect schemas without leaving your IDE
- QA Teams — verify monitor statuses and test collections straight from your communication hub
- Technical Leads — automate organizational querying to orchestrate cross-functional API documentation smoothly
Built-in capabilities (9)
Get details and requests for a specific collection
Get variables and details for an environment
Get details and items for a specific workspace
APIs represent a higher-level grouping that can include multiple versions and schemas. List all API definitions
Collections are used to group and share related API requests. List all API collections
Environments allow for managing variables across different stages like development or production. List all environment variable sets
Mock servers simulate API responses before the actual API is implemented. List all configured mock servers
Monitors help ensure API performance and availability. List all scheduled collection monitors
Workspaces are the primary organizational unit in Postman. List all accessible Postman workspaces
Why VS Code Copilot?
GitHub Copilot Agent mode brings Postman data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Postman in VS Code Copilot
Postman and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Postman to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Postman in VS Code Copilot
The Postman MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Postman for VS Code Copilot
Every tool call from VS Code Copilot to the Postman MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details of a specific collection just by providing its ID?
Yes! Use the get_collection_details tool with the unique ID. Your agent will respond with complete structure, requests, and metadata in seconds.
How do I check my API monitors status?
Simply ask the agent to run the list_monitors tool. It will compile all scheduled monitors and their latest results configured for your environment.
Does the integration permit modifying collections?
No. The core set of tools focuses strictly on querying and analyzing API context—listing workspaces, collections, and environments. State alteration operations are not currently exposed.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.