Bruno MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRUNO_MCP_CONFIG | No | Path to the bruno-mcp.config.json configuration file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bruno_run_requestB | Run a specific request from a Bruno collection |
| bruno_run_collectionB | Run all requests in a Bruno collection or specific folder |
| bruno_list_requestsB | List all requests in a Bruno collection |
| bruno_health_checkA | Check the health status of the Bruno MCP server and Bruno CLI |
| bruno_discover_collectionsB | Discover Bruno collections in a directory tree |
| bruno_list_environmentsB | List all environments in a Bruno collection |
| bruno_validate_environmentB | Validate an environment file in a Bruno collection |
| bruno_get_request_detailsA | Get detailed information about a specific request without executing it |
| bruno_validate_collectionB | Validate a Bruno collection's structure and configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clear, distinct purpose: discovery, detail retrieval, health checking, listing, running, and validation. No two tools overlap in functionality, making it easy for an agent to select the correct one.
All tools follow a consistent verb_noun pattern with the 'bruno_' prefix (e.g., bruno_discover_collections, bruno_run_request). The naming is predictable and uses the same snake_case convention throughout.
With 9 tools, the server covers the essential operations for interacting with Bruno collections without being overwhelming. Each tool addresses a necessary action, and the count is well-scoped for the server's purpose.
The toolset provides comprehensive coverage for inspecting, running, and validating Bruno collections and environments. While it lacks create/update/delete operations, these are out of scope for a read/run-oriented server, so there are no obvious gaps.