Skip to main content
Glama
tezaswiraj7222

mcp-postman-runner

by tezaswiraj7222
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-postman-runner

No user-submitted related servers found.

    Related Servers

    • postman-mcp-server

      ankit-roy-0602
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to create, manage, and interact with Postman collections, workspaces, environments, and API requests directly from conversations.
      24 npm
      5
      MIT

    • Postman MCP Server

      anarsyakir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Postman workspaces, collections, requests, responses, and monitors through the Postman API. Allows users to manage API collections, create and update requests/responses, and execute monitors directly from chat.
      17 npm
      MIT
    • thunderclient-mcp by thunderclient

      thunderclient-mcpofficial

      thunderclient
      A
      license
      B
      quality
      D
      maintenance
      Enables AI tools to create and manage API requests and collections in Thunder Client, with automated collection and folder creation.
      2
      24 npm
      11
      MIT

    • Postman MCP Generator

      ramborau
      F
      license
      Not graded
      quality
      D
      maintenance
      Automatically converts Postman API collections into MCP-compatible tools for AI assistants. Enables users to interact with any API through natural language by generating JavaScript tools from Postman requests.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing folders, previewing without execution, running a folder, and running a single request. The overlap between folder and request scoping is handled by explicit tool names and descriptions, so no ambiguity remains.

    Naming Consistency5/5

    All four tool names follow the consistent verb_noun pattern (list_folders, preview_requests, run_folder, run_request) using lowercase with underscores. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    Four tools is well-scoped for a Postman runner server. Each tool covers a necessary step in the workflow: discover, preview, execute folder, execute single request, without unnecessary additions.

    Completeness5/5

    The tool surface fully covers the domain of running Postman collections: listing folders to identify targets, previewing to verify safety, executing whole folders, and re-running individual requests. No obvious missing operations or dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources