Skip to main content
Glama
giovannicocco

Postman Tool Generation MCP Server

Related Servers

Alternatives to Postman Tool Generation MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that converts Postman API requests into executable tools for LLMs using the Postman Runtime. It supports complex authentication types and enables seamless integration between Postman collections and MCP clients like Claude Desktop.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Postman API requests as tools, enabling natural language interaction with APIs via MCP-compatible clients.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Generates MCP servers from Postman API requests, automatically creating JavaScript tools that enable LLMs to interact with any API documented in Postman collections. Supports authentication configuration and deployment via STDIO or SSE.
      -
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides seamless integration with the Postman API, enabling AI assistants and applications to interact with Postman workspaces, collections, requests, environments, and folders programmatically.
      19
      14 npm
      31
      MIT
    • 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.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server generated from Postman API requests, enabling natural language interaction with Postman collections via MCP-compatible clients like Claude.
      -

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.

    Tool Count2/5

    One tool is too few for the server's stated purpose of 'Postman Tool Generation,' which implies a broader scope like generating, managing, or testing tools. A single generation tool feels thin and incomplete for this domain.

    Completeness2/5

    The tool surface is severely incomplete for the inferred domain of Postman-based tool generation. There are obvious gaps, such as no tools for listing, editing, deleting, or testing generated tools, which limits agent workflows to a single action.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues