Bruno for API testing
Bruno keeps API collections as plain files in the repo, and its MCP server runs them through the Bruno CLI. That git-native, offline-friendly model is why it lands as our second pick for API testing: no cloud account, no synced workspace, just the .bru files already sitting next to your code.
The server is a thin bridge. It shells out to the Bruno CLI and hands back the test results, so an agent can run a saved collection and read whether the assertions passed. For driving a full request-by-request session against a stored, cloud-backed workspace, Postman does more, which is why it ranks ahead.
How Bruno fits
There is one tool here, and it does the job it claims: run-collection executes a Bruno collection through the Bruno CLI, takes an optional environment file and variable overrides, and returns the test output to the agent. If your team already writes requests and assertions as .bru files committed to the repo, the agent runs the suite against your real definitions and reports back what broke, with no separate account to provision.
The limit is the single entry point. There is no tool to build a request interactively, inspect one live response in isolation, or edit a collection from the conversation; the agent works with what is on disk and gets back a pass/fail report. Postman, our top pick, drives individual requests and saves them against a hosted workspace, so it fits exploratory, one-request-at-a-time testing better. Apidog covers design-and-test against a shared spec, and Playwright handles API checks woven into browser end-to-end flows. Reach for Bruno when the collection is in the repo and you want it run, not authored, by the agent.
Tools you would use
| Tool | What it does |
|---|---|
| run-collection | Runs a Bruno collection using the Bruno CLI and returns the test results, with optional environment file and override variables. |
FAQ
- Does Bruno's MCP server need a cloud account?
- No. It runs your local Bruno collections through the Bruno CLI, so it works against the .bru files in your repo with no synced workspace or login. That offline, git-native setup is the main reason to pick it over the others.
- Can the agent build or edit requests with Bruno's server?
- Not through this server. It exposes a single tool, run-collection, which executes an existing collection and returns the test results. To author requests interactively from the conversation, Postman is the stronger fit.