Postman MCP Server

Created By
freebeiroa year ago
A simple API wrapper around Postman/Newman functionality for API testing and mock server generation
Overview

What is Postman MCP Server?

Postman MCP Server is a Node.js Express application that serves as an API wrapper around Postman/Newman functionality, enabling users to manage Postman collections, create mock servers, and run API tests.

How to use Postman MCP Server?

To use the Postman MCP Server, clone the repository, install the dependencies, configure your environment with your Postman API key, and run the server. You can then access various API endpoints to create test scenarios, generate mock servers, and run tests.

Key features of Postman MCP Server?

  • Test scenario management using Postman collections.
  • Mock server generation based on Postman collections.
  • API testing capabilities using Newman.

Use cases of Postman MCP Server?

  1. Managing and executing API tests in a development environment.
  2. Creating mock servers for testing API responses.
  3. Organizing and running test scenarios for various API endpoints.

FAQ from Postman MCP Server?

  • What are the prerequisites for using Postman MCP Server?

You need Node.js (v14 or higher), npm or yarn, and a Postman API key.

  • How do I run the server?

After installation, run the command npm start to start the server.

  • Can I create multiple mock servers?

Yes, you can create multiple mock servers based on different Postman collections.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
freebeiro
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago