Skip to main content
Glama

Related Servers

Alternatives to Gostman

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Agent-native API client for executing REST, GraphQL, WebSocket, SSE, and gRPC requests from MCP-capable agents, with token-efficient responses and file-based collections.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      API client with an MCP server. Your agent builds collections from your codebase, runs requests, writes e2e flows, and exports them to GitHub Actions CI automatically. Category: Developer Tools
      0
      4
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      A keyboard-first API client that stores requests and environments as plain files, and exposes its workspace over MCP so agents can browse, send, and create requests with vault access.
      304 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Runs, tests and edits the saved HTTP requests in a Kurlo API workspace (Git-backed YAML): list collections and environments, send requests with their auth and pm.* tests, write new requests and tests, and diagnose the last failure. Secret values are sent to the API but masked in every tool result, and protected environments are refused.
      15
      29
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Lets an AI agent discover and call the APIs of a running service — gRPC, REST/OpenAPI, GraphQL, SignalR, MQTT, WebSocket and more — and record, replay, mock and assert on those calls. Calls only go to allowlisted URLs, and tools that change state ask for confirmation first.
      25
      12
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action or resource: request listing/reading/saving/sending, folder runs, last-response inspection, environment selection, variable setting, import, linting, secret scanning, load testing, and mock lifecycle. Adjacent tools like set_environment vs set_variables and send_request vs run_folder are sharply scoped by their descriptions.

    Naming Consistency4/5

    Most names are snake_case and follow a verb_noun pattern such as list_requests, send_request, start_mock, and scan_secrets. A few state getters (mock_status, last_response) deviate from the pure verb_noun pattern but remain readable and predictable.

    Tool Count4/5

    With 16 tools, the set is just above the ideal 3-15 range, but the server covers a broad API-workspace domain including requests, runs, environments, import, linting, secrets, mocking, and load testing. Each tool appears to earn its place, and there is no obvious redundancy.

    Completeness3/5

    Core workflows are covered: request list/get/save/send/run/import, environment selection and variable setting, linting, secret scanning, mock start/stop/status, and load testing. However, there is no delete or remove operation for saved requests or environments, and environment lifecycle support is only partial (list/select/set variables, but no create/delete).

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive