Community Servers · MODEL CONTEXT PROTOCOL
djkz bruno api mcp
MCP that allows us to load our bruno collection and have AI call it on our behalf
WHAT IT CONNECTS
What djkz bruno api mcp gives an AI Agent
- Automatic conversion of Bruno API collections to MCP tools
- Environment management for different API configurations
- HTTP with SSE transport
- Cross-origin support
- Built-in tools for API collection management
- Install dependencies:
- Start the server with your Bruno API collection:
- `--bruno-path` or `-b`: Path to your Bruno API collection directory (required)
- `--environment` or `-e`: Name of the environment to use (optional)
- `--include-tools`: Comma-separated list of tool names to include, filtering out all others (optional)
- `--exclude-tools`: Comma-separated list of tool names to exclude (optional)
- Connect from clients:
- Local connection: `http://localhost:8000/sse`
- From Windows to WSL: `http://<WSL_IP>:8000/sse`
- Get your WSL IP with: `hostname -I | awk '{print $1}'`
- `bruno-parser`: Bruno API collection parsing and environment handling
- `bruno-request`: Request execution and response handling
- `bruno-tools`: Tool creation and registration with MCP server
- No parameters required
- Returns:
- List of available environments
- Currently active environment
- Parameter: `message` (string)
SECURITY
An MCP listing is not a security review
An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.