Skip to main content
Glama
SalehKhatri

postman-mcp

by SalehKhatri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to postman-mcp

No user-submitted related servers found.

    Related Servers

    • Postman MCP Generator

      Ucode-io
      F
      license
      B
      quality
      D
      maintenance
      A server that implements the Model Context Protocol (MCP) standard, enabling LLMs like Claude to interact with selected Postman API requests through generated JavaScript tools.
      4
      -

    • Postman MCP Generator

      harichandra599
      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.
      -

    • Postman Tool Generation MCP

      giovannicocco
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that generates AI agent tools from Postman collections and requests. This server integrates with the Postman API to convert API endpoints into type-safe code that can be used with various AI frameworks.
      1
      13
      MIT

    • Postman MCP Server

      cogni-dao
      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.
      -
    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

    B3.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Workspaces, collections, requests, environments, and folders are cleanly separated, with no two tools appearing to do the same thing. The CRUD operations for each resource are unambiguous.

    Naming Consistency4/5

    The naming pattern is overwhelmingly consistent, using verb_noun in snake_case (e.g., list_workspaces, get_collection, update_environment). The only deviation is 'add_request' instead of 'create_request', which slightly disrupts the otherwise uniform create/update/delete pattern.

    Tool Count4/5

    At 19 tools, the count is slightly above the ideal 3-15 range but still reasonable for the breadth of Postman resources covered. Each tool has a clear purpose, and none feel redundant or unnecessary.

    Completeness3/5

    Collections and environments have full CRUD coverage, but requests lack read/list operations, folders only support create/delete, and workspaces miss delete. These gaps create minor dead ends that agents may need to work around when managing certain resources.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources