Skip to main content
Glama
deenesjakoruzh
hungthai1401

Bruno MCP

by hungthai1401
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ブルーノMCPサーバー

鍛冶屋のバッジ

Brunoコレクションの実行を可能にするMCP（Model Context Protocol）サーバー。このサーバーにより、LLMはBrunoを使用してAPIテストを実行し、標準化されたインターフェースを通じて詳細な結果を取得できます。

特徴

  • Bruno CLI を使用して Bruno コレクションを実行する

  • 環境ファイルのサポート

  • 環境変数のサポート

  • 詳細なテスト結果には以下が含まれます:

    • 全体的な成功/失敗のステータス

    • テストの概要（合計、合格、不合格）

    • 詳細な障害情報

    • 実行タイミング

Related MCP server: bruno-mcp

インストール

Smithery経由でインストール

Smithery経由で Claude Desktop 用の Bruno MCP Server を自動的にインストールするには:

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

手動インストール

# Install dependencies
npm install

# Build the project
npm run build

構成

~/Library/Application Support/Claude/claude_desktop_config.jsonにある Claude デスクトップ構成ファイルにサーバーを追加します。

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

利用可能なツール

ランコレクション

Bruno コレクションを実行し、テスト結果を返します。

パラメータ:

  • collection （必須）: ブルーノコレクションへのパス

  • environment （オプション）: 環境ファイルへのパス

  • variables （オプション）: キーと値のペアとしての環境変数

応答例:

{
  "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
  }
}

クロードでの使用例

Claude でサーバーを使用するには、Bruno コレクションを実行するように要求します。

「/path/to/collection.bru で Bruno コレクションを実行し、すべてのテストに合格したかどうかを教えてください」

クロードは次のことを行います:

  1. 実行収集ツールを使用する

  2. テスト結果を分析する

  3. 人間に分かりやすい実行概要を提供する

発達

プロジェクト構造

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

テストの実行

# Run tests
npm test

# Run tests with coverage
npm test:coverage

建物

# Build the project
npm run build

# Clean build artifacts
npm run clean

ライセンス

マサチューセッツ工科大学

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.

  1. 1 tool update
    • First observedrun-collection
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

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

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
    61 npm
    35
    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.
    30 PyPI
    4
    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

Appeared in Searches