bruno-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRUNO_MCP_BRU | No | Bruno CLI executable name or path. The executable is invoked directly, never through a shell. | bru |
| BRUNO_MCP_ROOT | No | Existing directory that contains the accessible collections. The path is resolved to its canonical location at startup, and collection access is confined to it. | current working directory |
| BRUNO_MCP_LOG_LEVEL | No | Minimum stderr log level: error, warn, info, or debug. | info |
| BRUNO_MCP_TIMEOUT_MS | No | Per-run timeout in milliseconds. Must be a positive integer. Values above 900000 are capped at 900000 (15 minutes). | 120000 |
| BRUNO_MCP_ALLOW_INSECURE | No | Permits callers to disable normal TLS certificate verification for a run when true. It does not disable verification by default. | false |
| BRUNO_MCP_MAX_REPORT_BYTES | No | Maximum accepted Bruno JSON reporter size in UTF-8 bytes (5 MiB by default). It must be a positive integer. | 5242880 |
| BRUNO_MCP_ALLOW_DEVELOPER_SANDBOX | No | Permits callers to request Bruno's developer sandbox when true. It does not enable developer mode by default. | false |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bruno_list_collectionsB | List Bruno collections available in the workspace. |
| bruno_list_requestsB | List and search requests in a Bruno collection. Returns request paths, names, types, and HTTP metadata. |
| bruno_get_requestB | Read a Bruno request. Use responseMode=revision for revision check, or full for parsed content. |
| bruno_list_environmentsA | List environments available to a Bruno collection without exposing variable values. |
| bruno_get_environmentB | Inspect a Bruno environment. Variables marked as secrets are always redacted. |
| bruno_runA | Execute requests, folders, or an entire Bruno collection using Bruno CLI v4. Returns structured execution results. Do not pass credentials or other secrets through variables. MCP tool arguments may be visible to the model and host. |
| bruno_search_requestsB | Search requests across all collections in the workspace. Returns matching requests with collection id. |
| bruno_create_requestA | Create a Bruno HTTP request YAML file. Missing parent folders are created and existing files are not overwritten. |
| bruno_update_requestA | Patch an existing Bruno HTTP request while preserving untouched content. Use expectedRevision="*" to patch latest version without preflight. |
| bruno_create_environmentA | Create a new Bruno environment file. Secret values must be omitted or [REDACTED]. |
| bruno_update_environmentB | Update an existing Bruno environment file. Existing secrets must be preserved with secret: true. |
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 11 tools
Most tools target distinct resources and actions clearly. The main ambiguity is between bruno_list_requests, which can also search within a collection, and bruno_search_requests, which searches across all collections.
The bruno_ prefix with verb_noun naming is highly consistent across nearly all tools. bruno_run is a minor deviation because it lacks a noun object, but it is still understandable given it runs requests, folders, or collections.
Eleven tools is well-scoped for a Bruno API client server covering collections, requests, environments, and execution. Each tool has a clear role in the overall workflow.
The tool surface covers listing, getting, creating, updating, searching, and running requests, plus environment management. The notable gap is the absence of delete operations for requests, environments, or collections.