Skip to main content
Glama
runninghare

REST-to-Postman MCP

by runninghare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to REST-to-Postman MCP

No user-submitted related servers found.

    Related Servers

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

    • Postman MCP

      logesh-works
      A
      license
      Not graded
      quality
      A
      maintenance
      Sync your API code into Postman collections — body, params, auth, responses, tests, and examples — with zero manual fill, straight from Claude Code.
      1
      MIT

    • Postman MCP Server

      sondang91
      A
      license
      A
      quality
      D
      maintenance
      Integrates Postman with Cursor IDE to manage collections and requests through natural language. It features specialized tools for automatically migrating API endpoints and metadata directly from .NET controller code into Postman collections.
      8
      74 npm
      MIT

    • Codebase Insights MCP Server

      llanterme
      A
      license
      Not graded
      quality
      C
      maintenance
      Analyzes API codebases from GitHub and Bitbucket repositories to generate Postman collections, business reports, and detailed code insights. Supports multiple frameworks including FastAPI, Spring Boot, Flask, Express, and OpenAPI/Swagger specifications.
      MIT
    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

    A3.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one handles Postman collections (API endpoint configurations), while the other handles Postman environments (environment variables). There is no overlap in functionality, making it impossible to confuse them.

    Naming Consistency5/5

    Both tools follow a perfect 'rest_to_postman_' prefix pattern with descriptive suffixes ('collection' and 'env'). The naming is completely consistent in style and structure throughout the set.

    Tool Count2/5

    With only 2 tools, this server feels severely under-scoped for a REST-to-Postman integration purpose. A complete synchronization system would typically need tools for operations like listing collections/environments, deleting resources, or handling authentication flows, not just create/update operations.

    Completeness2/5

    The toolset is significantly incomplete for REST-to-Postman synchronization. While create/update operations exist for collections and environments, there are no tools for reading existing resources, deleting them, managing workspaces, or handling more complex Postman features like monitors or mocks. This creates dead ends for agents trying to perform full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources