Skip to main content
Glama
morgenjacob-debug

Postman MCP Server

Related Servers

Alternatives to Postman MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      49 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to import and export Postman collections, author and execute API requests, run collection tests with pm.* scripts, manage environments and request history, and inspect legacy Postman data through 23 structured tools.
      8 npm
      5
      MIT
    • 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.
      13 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Postman’s remote MCP server connects AI agents, assistants, and chatbots directly to your APIs on Postman. Use natural language to prompt AI to automate work across your Postman collections, environments, workspaces, and more.
      42
      12,400 npm
      325
      Apache 2.0
    • A
      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.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables uploading and managing Postman collections, environments, and data files for API testing. Integrates with AI hosts via Model Context Protocol for test execution and result management.
      MIT

    TDQS

    B3.1/5.0

    Scored across 42 tools

    Disambiguation2/5

    Several inverse operation pairs are easy to confuse, such as syncCollectionWithSpec/syncSpecWithCollection, getSpecCollections/getGeneratedCollectionSpecs, and generateSpecFromCollection/generateCollection. The large set of spec-related getters (getSpec, getSpecDefinition, getSpecFile, getSpecFiles) also creates unclear boundaries that could lead to misselection.

    Naming Consistency3/5

    Most tools follow a snake_case verb_noun pattern, but the set mixes create/generate, get/getAll, and update/put (putCollection/putEnvironment vs. update*). The sync and generation pairs use confusingly swapped phrases, making the naming readable but noticeably inconsistent.

    Tool Count2/5

    42 tools is well beyond the typical 3-15 well-scoped range and falls into the 25+ category. Although Postman covers many resource types, this many tools creates significant selection overhead without clear grouping.

    Completeness3/5

    Coverage spans collections, specs, environments, mocks, and workspaces with create/get/update operations. However, there are no delete operations at all—such as deleteCollection, deleteEnvironment, deleteWorkspace, or deleteSpec—which is a notable lifecycle gap that agents cannot work around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues