Skip to main content
Glama
hungthai1401

Bruno MCP

by hungthai1401
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Bruno MCP

No user-submitted related servers found.

    Related Servers

    • bruno-mcp

      jackmulligan-ire
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that executes requests from Bruno API collections via the Bruno CLI tool, enabling API request execution and collection management.
      4
      MIT

    • bruno-mcp

      gpact
      A
      license
      A
      quality
      A
      maintenance
      A local MCP server that lets clients discover, inspect, and execute Bruno OpenCollection API collections, while delegating request execution, authentication, scripting, assertions, and environment resolution to the Bruno CLI.
      11
      10 npm
      1
      MIT

    • Bruno MCP Server

      macarthy
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server that enables programmatic creation and management of Bruno API testing collections, environments, and requests through standardized MCP tools.
      1
      85 npm
      33
      MIT

    • bruno-headless

      bachden
      A
      license
      Not graded
      quality
      C
      maintenance
      A headless MCP server for Bruno workspaces, enabling CRUD operations on collections, folders, requests, environments, and dotenv files, plus request execution with scripting, tests, and assertions over HTTP, GraphQL, gRPC, and WebSocket.
      MIT

    • API Testing MCP

      cocaxcode
      A
      license
      A
      quality
      D
      maintenance
      A lightweight, local-first MCP server for executing HTTP requests and managing API collections and environments without cloud dependencies. It enables testing APIs, handling authentication, and importing OpenAPI specifications directly within MCP-compatible workflows.
      42
      50 npm
      9
      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

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool 'run-collection' has a single, clearly defined purpose that cannot be misselected against other tools.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'run-collection' follows a verb-noun pattern, and there are no other tools to compare it against for inconsistency.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. While it could be appropriate for a very specific task, it often feels thin and lacks the breadth needed for typical agent workflows.

    Completeness1/5

    With only one tool, the surface is severely incomplete. There are obvious gaps, such as the inability to create, list, update, or delete collections, which are typical operations in a collection management domain. This will likely cause agent failures when trying to perform basic tasks beyond running a collection.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources