Boosthis vs Bugsnag MCP
A side-by-side look at the Boosthis and Bugsnag MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BoosthisMonitoring · Remote HTTP/SSERead-only performance insights for your Boosthis projects: speed, crashes, traces, and fixes.40FairAuth: no auth requiredVerdict: choose Boosthis for monitoring work over a hosted endpoint; choose Bugsnag MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose Boosthis when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Bugsnag MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BUGSNAG_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Boosthis | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 40/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | BUGSNAG_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 25 |
| Directory activity | 7 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Boosthis | View Bugsnag MCP |
Tools & capabilities
Boosthis tools
No tool names declared yet. Check the project README from the listing page.
Bugsnag MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
Boosthis
{
"mcpServers": {
"boosthis": {
"command": "npx",
"args": [
"-y",
"boosthis"
]
}
}
}
Bugsnag MCP
{
"mcpServers": {
"tgeselle-bugsnag-mcp": {
"command": "npx",
"args": [
"-y",
"bugsnag-mcp-server"
],
"env": {
"BUGSNAG_API_KEY": "YOUR_BUGSNAG_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Boosthis is categorized under Monitoring and uses a remote HTTP/SSE transport. Bugsnag MCP belongs to Monitoring and uses a local stdio subprocess. Pick Boosthis for monitoring work and Bugsnag MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Boosthis has no declared pricing — check the project's own site. Auth: no auth required. Bugsnag MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add boosthis and tgeselle-bugsnag-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Boosthis has a quality signal of 40/100 (Fair) with 7 views, 0 installs and 0 GitHub stars. Bugsnag MCP has 41/100 (Fair) with 0 views, 0 installs and 25 GitHub stars.