Skip to main content
Glama
568,621 tools. Updated 2026-09-14 21:37

"postman" matching MCP tools:

Matching MCP Servers

  • 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
    3,622 npm
    312
    Apache 2.0
  • 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
    13 npm
    31
    MIT

Matching MCP Connectors

  • Give your AI agents trusted access to the full Postman platform.

  • Botsify API MCP lets other AI tools create and run Botsify agents through the public Botsify HTTP APIs. Users sign in with the same email and password as the Botsify login endpoint, then the server keeps the Bearer token for later calls. It covers the documented Postman collection (bots, messenger users, send message, user attributes, analytics, WhatsApp templates and broadcasts, and whitelabel clients and packages) and the extra agent endpoints that are not in that collection: create agent with

  • Retrieve Postman billing account details for teams to manage subscriptions and track usage.
    MIT
  • Import an API spec (OpenAPI, Swagger, Postman) to create a draft bolthub listing with endpoints and default pricing. Re-importing shows a diff instead of duplicating.
    MIT
  • Create a mock server for a Postman collection to simulate API responses and enable testing without a live backend.
    Apache 2.0
  • Search Postman entities such as requests, collections, workspaces, specs, flows, environments, mocks, and documents by query and filters. Find internal or public API resources across your organization and the Postman network.
    Apache 2.0
  • Replace a Postman collection's contents with a new collection body. Provide the collection ID and updated data, or omit item IDs to recreate them.
    Apache 2.0
  • Export an API specification as OpenAPI YAML, JSON, or Postman Collection. Use this to get the finished document out; to check it against the standard first use validate_spec. Requires project context.
    MIT
  • Creates a new file for an OpenAPI or protobuf 2/3 specification. Add JSON or YAML spec files to Postman, with auto-created folders for nested paths.
    Apache 2.0
  • Retrieve active mock servers from Postman. Scope results by workspace ID or team ID; use workspace when known, otherwise provide team ID.
    Apache 2.0
  • Create API specifications in Postman's Spec Hub with support for OpenAPI, AsyncAPI, protobuf, GraphQL, and Smithy. Manage single or multi-file specs directly from your workspace.
    Apache 2.0
  • Execute a Postman collection by ID to obtain detailed test results and execution statistics. Optionally pass an environment ID for variable substitution.
    Apache 2.0
  • Update a workspace's name, visibility, description, or summary. Set new values for workspace properties to manage your Postman workspaces.
    Apache 2.0