bruno-mcp
Related Servers
Alternatives to bruno-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA local MCP server that lets clients discover, inspect, and execute Bruno OpenCollection API collections, while delegating request execution, authentication, scripting, assertions, and environment resolution to the Bruno CLI.1110 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that executes requests from Bruno API collections via the Bruno CLI tool, enabling API request execution and collection management.4MIT
- MIT
- AlicenseBqualityFmaintenanceA Model Context Protocol (MCP) server that enables programmatic creation and management of Bruno API testing collections, environments, and requests through standardized MCP tools.185 npm33MIT
- AlicenseAqualityDmaintenanceA read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.914 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Swagger/OpenAPI metadata efficiently from AI tools, enabling fast API discovery, search, and schema inspection.620 npmMIT
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.