@ostico/bruno-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @ostico/bruno-mcp@2.5.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
list_collections | Returned a result under 0.1 s · 133 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Very long description in
run_collection:3000 characters or more
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
create_collection name, description, baseUrl, outputPath, ignore, format, workspacePath, registerInWorkspace
Create a new Bruno API testing collection with configuration. outputPath is the PARENT directory and name is appended to it: outputPath "/work/apis" with name "Billing" creates the collection at /work/apis/Billing. Do not put the collection name in outputPath as well. The new collection is also added to the workspace registry that `list_collections` reads rather than the disk, so a collection missing from it is invisible to that tool and to the Bruno app. The result says whether it was registered and, if not, why.
create_environment collectionPath, name, variables, overwrite
Create an environment file for a Bruno collection. Writes the WHOLE file, so it REFUSES a name that already exists rather than overwriting it — the error names the existing variables and which ones a replace would delete, so you can merge with update_environment, pick another name, or retry with overwrite: true.
update_environment collectionPath, name, variables
Partially update an existing Bruno environment by MERGING the provided variables into the existing ones. Variables not listed are preserved, unlike create_environment, which replaces the whole file.
set_environment_variable collectionPath, environment, name, value, enabled, secret
Set (add or update) a single variable in an existing Bruno environment. MERGES into the environment — all other variables are preserved.
remove_environment_variable collectionPath, environment, name
Remove a single variable from an existing Bruno environment. MERGES into the environment — all other variables are preserved.
13 more tools
write_request collectionPath, name, filePath, filename, kind, method, url, headers, body, auth, query, pathParams, assert, vars, settings, websocket, grpc, folder, sequence, scripts, scriptMode, requests
Create a request file or change an existing one (.bru and .yml). The locator decides which: collectionPath plus name creates, filePath changes what is already there. Creating never overwrites — an existing file is refused, so address it by filePath. Changing is a partial merge: only provided fields are updated and every other field is preserved. Pass requests to write a whole set in ONE call, not one call per request. Authors HTTP requests by default, WebSocket requests with kind "websocket" (url plus websocket.messages) and gRPC requests with kind "grpc" (url plus grpc.method, grpc.protoPath and grpc.messages); neither takes an HTTP method or a body. Supports multipart/form-data with file uploads and per-part contentType (body.type "form-data" with formData entries of type "file"), and inline scripts (pre-request/post-response/tests) so no separate add_test_script call is needed. Scripts run as async functions: top-level await works, and bru.sleep(ms)/setTimeout/setInterval spend the script timeout (settings.timeout, default 5000ms) — raise it via the settings argument. Inline scripts REPLACE the existing script of the same type by default, so repeated calls do not accumulate duplicate blocks; scriptMode:"append" concatenates instead, and remove_script clears one. RENAMING: name and filename are independent, as they are in Bruno itself — name changes the request's name inside the file and filename moves the file. Pass both to keep them in step, and read the new path back from the response.
move_request filePath, targetCollectionPath, targetFolder, copy
Relocate a request file to another folder, or to another collection entirely. Pass copy:true to duplicate it instead of moving it. The bytes are moved verbatim, nothing is parsed and rewritten, so seq arrives unchanged and may tie with a request already there; that is reported, and Bruno breaks such a tie by filename. The file keeps its name: use write_request with filename to rename it. The new path comes back in the response.
add_test_script bruFilePath, scriptType, script, scriptMode
Add pre-request, post-response, or tests scripts to a Bruno request. Canonical scriptType values are pre-request/post-response/tests; the aliases before-request (→ pre-request) and after-response (→ post-response) are also accepted. Appends to any existing script of that type by default — pass scriptMode:"replace" to overwrite it, or use remove_script to clear it. Assertions must be wrapped in test("name", function() { ... }) to be reported. Scripts run as async functions: top-level await works, and bru.sleep(ms), setTimeout and setInterval spend the script timeout (settings.timeout, default 5000ms), which write_request's settings argument raises.remove_script bruFilePath, scriptType
Delete a pre-request, post-response, or tests script from a Bruno request, leaving the rest of the request intact, including duplicate blocks accumulated by appending. Canonical scriptType values are pre-request/post-response/tests; the aliases before-request and after-response are accepted. Removing all scripts also drops the now-empty script container.
delete_request filePaths, confirm
Permanently delete request files from a Bruno collection. One confirm covers the whole list. Each file is unlinked and cannot be recovered through this server. Only .yml/.bru files inside a detected collection can be deleted. Every path is checked before the first unlink, so one unusable path deletes nothing. The result names each file's outcome. To clear a script and keep the request, use remove_script.
list_collections workspacePath
List the Bruno collections REGISTERED IN workspace.yml, with their names and paths. This is a registry listing, not a filesystem scan: a collection that exists on disk but is not registered will NOT appear, and registered entries that no longer exist are returned with "exists": false. A known absolute path works in the other tools without appearing here. Use the returned path as collectionPath in get_collection_stats, list_requests and run_collection.
list_requests collectionPath
List all request files (.yml/.bru) in a Bruno collection. Returns absolute file paths, each usable as an entry in the requests list of run_collection, or of one of its groups.
get_collection_stats collectionPath, folder, method, nameContains, includeRequests
Get statistics about a Bruno collection — request counts by method, folders, environments, and per-request details including each request's file path and URL. environmentDetails lists each environment with the NAMES of the variables it declares, values withheld, so what an environment already defines is visible before merging into it with set_environment_variable. Use filePath values as entries in the requests list of run_collection. SIZE: the per-request array is the bulk of the response and grows with the collection — a few hundred requests run to tens of kilobytes. Narrow it with folder, method or nameContains, or pass includeRequests: false for counts only. The counts always describe the WHOLE collection; a filtered call adds matchedRequests so the two cannot be confused.
run_collection collectionPath, environment, collectionRoot, requests, groups, data, dataFile, parallel, maxConcurrency, bail, includeResponseBody, maxResponseBodyBytes, includeResponseHeaders, maxResponseHeaderBytes, variables, captureVariables, websocket, report, cookieJar
Execute requests in a Bruno collection and run their test scripts. SUBSET: requests is an ORDERED list of .yml/.bru paths, absolute or relative to collectionPath; a directory expands recursively. Duplicates allowed, and run twice. Omit to run the whole collection. Pass requests OR groups, never both. GROUPS: one call, more than one identity or configuration. Each group owns its OWN variable store and cookie jar, so nothing a group sets — a bru.setVar, a session cookie — is visible to any other group. That is what makes running the same five requests as alice and as bob in one call safe. ITERATIONS: data or dataFile runs a group once per row, the row bound as variables. Each row is its own group — same name, own index, own iterationIndex — with that same isolation. Rows are independent: a failing row does not stop later rows. Ceiling 1000 rows per scope. PARALLELISM: parallel on the run fans groups out; parallel on a group fans that group's requests out. A group is serial unless it says otherwise, whatever the run does. seq no longer constrains execution — default order and reporting order only — so two requests in one parallel group run at the same moment and may contend on the store they share. startAfter holds a group until a named group has completed a given number of its requests, connecting a listener before a trigger fires; needs parallel on the run. Chains allowed; cycles, and gates that can never open, are refused before anything runs. If the group waited on ends early, the waiting group reports that as its error instead of starting. RESULTS are group-shaped: each groups[] entry carries its own summary, results, capturedVariableNames and capturedVariables; the top-level summary is the run. Run-wide warnings are top-level, so a captureVariables name is reported unset only when NO group set it. There is no top-level results array, not even with no groups. A crashed group reports error and counts as one failure. RESPONSE DATA: every result carries the response body (response_body, response_content_type, response_body_truncated) unless includeResponseBody is false; maxResponseBodyBytes caps it. Every result also carries response_headers, no test script needed; includeResponseHeaders false omits them, maxResponseHeaderBytes bounds one value, and includeResponseBody false bounds the body only, never the headers: credential-named values are masked, and set-cookie is a LIST — one entry per cookie — whose entries keep every attribute (HttpOnly, Secure, SameSite, Path, Max-Age) and withhold only the cookie value, so a cookie-flag or HSTS check is one call. A websocket result's response_headers hold its handshake response (the 101), the only place a session cookie or a negotiated sec-websocket-protocol is visible for that transport; a gRPC result reports metadata under grpc instead. ORDER: within a group, the order given; a directory expands by seq scoped to its own folder, subfolders before that folder's loose requests, ties by filename. An unparse
read_request filePath
Read a single request file back as structured JSON: method, url, headers, query and path params, body, auth mode, scripts, assertions, vars, settings and docs. Both .bru and .yml return the same shape, so the on-disk format stays invisible. Use this before write_request to see current state, and after it to confirm what was written. A websocket or grpc request also carries its stored messages in full — title, content, and for a websocket the type and whether the runner will send it — under websocket.messages or grpc.messages, keyed as write_request accepts them. A "notes" array reports anything the file declares that the runner will not act on.
read_environment collectionPath, name
Read an environment back as structured JSON: every variable with its value, plus its disabled and secret flags. Omit "name" to list the collection's environments instead. Secret variables are returned by name only — no file format stores a secret's value, so there is none to return.
unregister_collection collectionPath, workspacePath
Remove a collection from the workspace registry, leaving every file on disk untouched. list_collections reads that registry, so this is how an entry stops being listed, including a stale entry whose directory is gone. To delete the collection itself, use delete_collection.
delete_collection collectionPath, confirm, workspacePath
Permanently delete a Bruno collection: the collection directory and everything inside it is removed from disk, and its workspace registry entry with it. Nothing here can be recovered through this server. Only a directory that is itself a collection root — one holding opencollection.yml or bruno.json — can be deleted. To keep the files and only stop the collection being listed, use unregister_collection instead.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.0.0 |
| Source | github.com/Ostico/bruno-mcp-studio |
| Install scripts | protobufjs declare them. This runner does not run them. |
| Tarball | sha512-O9eJZF73VXzGniNz1Q5Wq1A6gwIc2ZMRZUEjReNZZiWU4Jvnp9ZOUepii62wHeYV/pebTv0x2t/ZRDl5J/4+iA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40ostico/bruno-mcp)
New version out? Ask for a fresh report.