Postman Tool Generation MCP Server

Created By
giovannicoccoa year ago
Overview

What is Postman Tool Generation MCP Server?

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. Automating the generation of API client code from Postman collections.
  2. Creating AI tools that interact with APIs seamlessly.
  3. Facilitating the integration of AI frameworks with existing API services.

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 a specific programming language required?

You can generate code in either TypeScript or JavaScript.

  • What AI frameworks are supported?

The server supports multiple frameworks including OpenAI, Mistral, Gemini, Anthropic, LangChain, and AutoGen.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
giovannicocco
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago