Bruno MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_PATH | Yes | The absolute path to your Bruno collection |
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 |
|---|---|
| list_bruno_requestsB | List all Bruno request files in the collection root. Optionally specify a project_path. |
| get_bruno_request_detailB | Get structured details and raw content of a specific Bruno request file. |
| run_bruno_requestB | Execute a Bruno API request using the local Bruno CLI and get status and outputs. |
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 3 tools
Each tool has a distinct purpose: listing files, getting details, and executing requests. There is no overlap in functionality.
All tool names follow the same verb_bruno_request pattern, making the naming predictable and consistent.
Three tools is a well-scoped, focused set for a Bruno request server. Each tool earns its place.
The server covers the core workflow of listing, inspecting, and running requests. Missing mutation operations (create/update/delete) are a minor gap but not critical for the server's apparent purpose.