Postman Agent Generator

Created By
jonicoa year ago
Overview

What is Postman Agent Generator?

Postman Agent Generator is a tool that creates an MCP-compatible server and automatically generates JavaScript tools for selected Postman API requests, enabling seamless integration with various APIs.

How to use Postman Agent Generator?

To use the Postman Agent Generator, install the necessary dependencies, set up environment variables, and run the generated MCP server using Node.js or Docker.

Key features of Postman Agent Generator?

  • Generates an MCP-compatible server (mcpServer.js).
  • Automatically creates JavaScript tools for each selected Postman API request.
  • Supports Docker deployment for production environments.
  • Allows easy addition of new tools through the Postman Agent Generator interface.

Use cases of Postman Agent Generator?

  1. Integrating multiple APIs into a single MCP server.
  2. Automating API requests for testing and development.
  3. Deploying API tools in a Docker container for production use.

FAQ from Postman Agent Generator?

  • What are the prerequisites for using this project?

You need Node.js (v16+ required) and npm installed on your machine.

  • Can I run the server with Docker?

Yes! The project includes a Dockerfile for easy deployment.

  • How do I add new tools to my agent?

Visit the Postman Agent Generator, select new API requests, generate a new agent, and copy the tools into your existing project.

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

a day ago