bruno-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_collectionsA | Returns the active Bruno collection and its endpoint count. |
| list_foldersB | Returns a paginated collection folder hierarchy. Use parent and depth to explore a subtree without loading the complete hierarchy. |
| list_endpointsC | Lists endpoint summaries, optionally filtered by method, request type, folder, or tags. |
| search_endpointsA | Searches endpoints with field-aware ranking. Returns score and matchedFields for every result; docs-only matches are excluded by default. |
| get_endpointB | Returns a complete sanitized endpoint contract by stable ID, or by exact method and normalized path. |
| get_endpointsA | Returns up to 25 complete sanitized endpoint contracts by stable ID in one call. Use include_examples only when complete saved responses are required. |
| get_endpoint_examplesB | Lean examples-only alternative to get_endpoint(include_examples: true). Returns saved status, content type, and complete response bodies without the full contract. |
| get_index_statusA | Returns index generation time, endpoint count, and parser warnings. |
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 8 tools
Each tool targets a distinct operation: listing collections, folders, endpoints, getting single/bulk endpoints, searching, examples, and index status. No overlap in functionality.
All tools follow the verb_noun pattern consistently, using 'list_' for enumeration and 'get_' for retrieval, with clear singular/plural distinctions (e.g., get_endpoint vs get_endpoints).
With 8 tools, the server is well-scoped for its purpose of inspecting Bruno API collections. Each tool has a clear role, and the count is neither too sparse nor excessive.
The tool surface covers all essential read operations for collections, folders, endpoints, and search. Missing write operations (create, update, delete) are outside the intended scope, though a tool to list tags or metadata could be a minor addition.