Skip to main content
Glama
kta41

mcp-bruno

by kta41
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-bruno

No user-submitted related servers found.

    Related Servers

    • 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
      14 npm
      1
      MIT

    • 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 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
      74 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
    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.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools have distinct primary purposes (listing, running, discovering, reading, validating). However, run-filter-scenarios and run-full-validation overlap in testing disabled query filters, requiring careful reading to choose between targeted filter testing and comprehensive two-phase validation.

    Naming Consistency5/5

    All tool names follow a consistent lowercase hyphen-separated verb_noun pattern (list-, run-, discover-, read-), with no mixed casing or verb styles.

    Tool Count5/5

    Seven tools is well-scoped for a Bruno collection runner/validator; each tool covers a distinct stage (discovery, execution, filtering, validation, artifact reading) without bloat.

    Completeness4/5

    The surface covers discovery, execution, filter validation, and artifact reading, which are the core lifecycle for running and validating collections. Minor gaps exist (e.g., no dedicated single-request execution or collection editing), but agents can work around them via run-collection and filter scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources