Skip to main content
Glama
deenesjakoruzh
hungthai1401

Bruno MCP

by hungthai1401
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Bruno MCP Server

Trust Score

An MCP (Model Context Protocol) server that enables running Bruno collections. This server allows LLMs to execute API tests using Bruno and get detailed results through a standardized interface.

Features

  • Run Bruno collections using the Bruno CLI

  • Support for environment files

  • Support for environment variables

  • Detailed test results including:

    • Overall success/failure status

    • Test summary (total, passed, failed)

    • Detailed failure information

    • Execution timings

Related MCP server: API Testing MCP

Installation

Installing via Smithery

To install Bruno MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @hungthai1401/bruno-mcp --client claude

Manual Installation

# Install dependencies
npm install

# Build the project
npm run build

Configuration

Add the server to your Claude desktop configuration file at ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "bruno-runner": {
      "command": "npx",
      "args": ["-y", "bruno-mcp"],
    }
  }
}

Available Tools

run-collection

Runs a Bruno collection and returns the test results.

Parameters:

  • collection (required): Path to the Bruno collection

  • environment (optional): Path to environment file

  • variables (optional): Environment variables as key-value pairs

Example Response:

{
  "success": true,
  "summary": {
    "total": 5,
    "failed": 0,
    "passed": 5
  },
  "failures": [],
  "timings": {
    "started": "2024-03-14T10:00:00.000Z",
    "completed": "2024-03-14T10:00:01.000Z",
    "duration": 1000
  }
}

Example Usage in Claude

You can use the server in Claude by asking it to run a Bruno collection:

"Run the Bruno collection at /path/to/collection.bru and tell me if all tests passed"

Claude will:

  1. Use the run-collection tool

  2. Analyze the test results

  3. Provide a human-friendly summary of the execution

Development

Project Structure

src/
  ├── index.ts           # Entry point
  ├── server.ts          # MCP Server implementation
  ├── runner.ts          # Bruno runner implementation
  └── types.ts           # Type definitions

Running Tests

# Run tests
npm test

# Run tests with coverage
npm test:coverage

Building

# Build the project
npm run build

# Clean build artifacts
npm run clean

License

MIT

Available Tools

1 tool
run-collectionC

Run a Bruno Collection using Bruno CLI

ParametersJSON Schema
NameRequiredDescriptionDefault
collectionYesPath to the Bruno collection
environmentNoOptional path to environment file
variablesNoOptional environment variables

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Run' which implies execution, but fails to describe critical behaviors like whether it's read-only/destructive, requires specific permissions, has side effects (e.g., file changes), or handles errors. This leaves significant gaps for an execution tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, clearly stating the core action without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of running a collection (an execution tool with potential side effects), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, output format, error handling, or dependencies, making it inadequate for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the schema already documents all parameters (collection path, optional environment file, optional variables). The description adds no additional meaning beyond what the schema provides, such as format examples or usage context, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Run') and resource ('a Bruno Collection using Bruno CLI'), making the purpose understandable. However, it doesn't differentiate from siblings since there are none, so it can't achieve the full 5 points for sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool, such as prerequisites (e.g., Bruno CLI installation), alternatives, or specific contexts. It only states what the tool does without usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedrun-collection
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
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

Related MCP Connectors

Related MCP Servers

  • 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
    87
    31
    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
    162
    6
    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

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hungthai1401/bruno-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server