run-collection
Run a Bruno Collection using Bruno CLI
Run a Bruno API collection from the conversation, picking the environment and overriding variables per run, and read the results back.
LABSCO SUMMARY
Collection, environment and variables are all arguments, so nothing about the suite has to change to make it callable, and the same collection can be pointed at a different target by name. Authoring stays in Bruno: there is no tool here for editing a request, inspecting one response in isolation, or managing environments, and the result you get is whatever the CLI run produced.
A single-tool wrapper over the Bruno CLI that executes a collection you point it at and returns what the run produced.
A Bruno collection on the machine and the Bruno CLI available to execute it. No account, no key and no environment variables of its own.
One command — npx -y bruno-mcp
USE CASES
Point it at the collection in the repository, name the environment to run against, and override the variables that differ for this run — a base URL, a token — without editing anything in the collection itself.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
run-collectionRun a Bruno Collection using Bruno CLI
BEFORE YOU INSTALL
1 tool when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"bruno-mcp": {
"command": "npx",
"args": [
"-y",
"bruno-mcp"
]
}
}
}npx -y bruno-mcp