Skip to main content
Glama
Ostico

Bruno MCP Studio

by Ostico
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Bruno MCP Studio

No user-submitted related servers found.

    Related Servers

    • Bruno MCP Server

      kodlbegiko
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to discover, inspect, and run API requests in Bruno collections locally, keeping all data private.
      3
      53 npm
      MIT

    • Bruno MCP Server

      jcr82
      A
      license
      A
      quality
      C
      maintenance
      Integrates Bruno CLI for API testing, enabling users to run API requests and collections, manage environments, generate test reports (JSON/JUnit/HTML), and validate collection structures through natural language commands.
      9
      53 npm
      5
      MIT

    • bru-mcp

      h-mergel
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Bruno CLI as tools for AI agents, allowing them to discover, inspect, and execute Bruno API collections through the MCP protocol.
      1
      MIT

    • MCP-Insomnia

      anggasct
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to create, manage, and execute API collections, requests, and environments in Insomnia-compatible formats. It supports direct synchronization with the local Insomnia app database and importing from OpenAPI, Postman, and cURL.
      30
      255 npm
      26
      MIT
    • thunderclient-mcp by thunderclient

      thunderclient-mcpofficial

      thunderclient
      A
      license
      B
      quality
      D
      maintenance
      Enables AI tools to create and manage API requests and collections in Thunder Client, with automated collection and folder creation.
      2
      24 npm
      11
      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 21 tools

    Disambiguation4/5

    Most tools pair a clear resource with a clear action—collection, environment, request, script—so an agent can usually tell them apart. The main boundary ambiguity is between create_collection, create_test_suite, and create_crud_requests (all generate collections/requests), and between add_test_script and the inline-script support in create_request/modify_request.

    Naming Consistency4/5

    The set mostly follows a consistent verb_noun pattern: create_collection, delete_request, list_requests, read_environment. Minor inconsistencies exist—add_test_script vs remove_script, and read_*/get_* verbs—but the overall convention is predictable.

    Tool Count3/5

    At 21 tools, the server sits in the heavy range. The breadth is partially justified by covering collections, environments, requests, scripts, generation, and execution, but several tools could be consolidated (e.g., set_environment_variable/remove_environment_variable vs update_environment), making the surface feel larger than necessary.

    Completeness3/5

    Collection, request, script, and execution workflows are well covered, and generation tools create test suites and CRUD operations. However, the environment lifecycle has an obvious gap: there is no delete_environment, and collection configuration/rename/move operations are also absent, leaving some dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources