Skip to main content
Glama
macarthy

Bruno MCP Server

by macarthy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Bruno MCP Server

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

    • postman-mcp

      SalehKhatri
      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
      17 npm
      31
      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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined and distinct purpose.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions.

    Tool Count2/5

    One tool is too few for a server's purpose, as it severely limits functionality and scope. This feels thin and incomplete for any meaningful domain coverage.

    Completeness2/5

    The server's purpose appears to be running Bruno Collections, but with only a 'run' operation, there are significant gaps. Missing operations like listing collections, creating collections, or managing them make the surface severely incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources