Postman Tool Generation MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Postman Tool Generation MCP Server?

The Postman Tool Generation MCP Server is a server that generates AI agent tools from Postman collections and requests, integrating with the Postman API to convert API endpoints into type-safe code for various AI frameworks.

How to use Postman Tool Generation MCP Server?

To use the server, install the dependencies, build the server, and configure the MCP settings. You can then use the generate_ai_tool function to create AI tools from your Postman collections.

Key features of Postman Tool Generation MCP Server?

  • Generates TypeScript/JavaScript code from Postman collections.
  • Supports multiple AI frameworks (OpenAI, Mistral, Gemini, Anthropic, LangChain, AutoGen).
  • Provides type-safe code generation with error handling and response validation.

Use cases of Postman Tool Generation MCP Server?

  1. Creating AI tools for API endpoints in Postman.
  2. Automating the generation of type-safe code for various AI frameworks.
  3. Simplifying the integration of APIs with AI models.

FAQ from Postman Tool Generation MCP Server?

  • Can I use this server with any Postman collection?

Yes! The server can generate tools from any valid Postman collection.

  • Is there support for multiple programming languages?

Yes! The server supports both TypeScript and JavaScript.

  • How do I handle errors during tool generation?

The server includes comprehensive error handling for invalid parameters, API failures, and network issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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