A side-by-side look at the AI and MCP Bruno MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI for developer tools work as a local process; choose MCP Bruno for developer tools as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | M MCP Bruno | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AI | View MCP Bruno |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"contentrain-ai": {
"command": "npx",
"args": [
"-y",
"contentrain"
]
}
}
}
{
"mcpServers": {
"mcp-bruno": {
"command": "uvx",
"args": [
"--from",
"mcp-bruno",
"bruno-mcp"
]
}
}
}