Postman MCP Generator

Created By
agentesqa year ago
Weaviate MCP Server
Overview

What is Postman MCP Generator?

Postman MCP Generator is a tool that creates a Model Context Provider (MCP) server, allowing users to automate API requests and integrate them with MCP-compatible clients.

How to use Postman MCP Generator?

To use the Postman MCP Generator, install Node.js and npm, run the installation command, set up environment variables in the .env file, and test the generated MCP server with Postman or connect it to an MCP client like Claude Desktop.

Key features of Postman MCP Generator?

  • Automatically generates an MCP-compatible server (mcpServer.js).
  • Creates JavaScript tools for each selected Postman API request.
  • Supports Docker deployment for production environments.
  • Provides CLI commands for listing tools and adding new ones easily.

Use cases of Postman MCP Generator?

  1. Automating API requests for various services.
  2. Integrating with MCP clients for enhanced functionality.
  3. Deploying API tools in production using Docker.

FAQ from Postman MCP Generator?

  • What are the prerequisites for using the Postman MCP Generator?

You need Node.js (v18+ recommended) and npm installed.

  • Can I deploy the MCP server using Docker?

Yes! The project includes a minimal Docker setup for production deployments.

  • How do I add new tools to my MCP server?

You can generate new tools using the Postman MCP Generator and copy them into your existing project's tools/ folder.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
agentesq
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)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago