Bugsnag MCP vs World Monitor
A side-by-side look at the Bugsnag MCP and World Monitor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bugsnag MCP for monitoring work as a local process; choose World Monitor for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose World Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 41/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | BUGSNAG_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 25 | 89,438 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Bugsnag MCP | View World Monitor |
Tools & capabilities
Bugsnag MCP tools
No tool names declared yet. Check the project README from the listing page.
World Monitor 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.
Bugsnag MCP
{
"mcpServers": {
"tgeselle-bugsnag-mcp": {
"command": "npx",
"args": [
"-y",
"bugsnag-mcp-server"
],
"env": {
"BUGSNAG_API_KEY": "YOUR_BUGSNAG_API_KEY_HERE"
}
}
}
}
World Monitor
{
"mcpServers": {
"world-monitor": {
"command": "npx",
"args": [
"-y",
"worldmonitor"
]
}
}
}
Frequently asked questions
Bugsnag MCP is categorized under Monitoring and uses a local stdio subprocess. World Monitor belongs to Monitoring and uses a local stdio subprocess. Pick Bugsnag MCP for monitoring work and World Monitor 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.
Bugsnag MCP has no declared pricing — check the project's own site. World Monitor is listed as free. Auth: other. 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 tgeselle-bugsnag-mcp and world-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bugsnag MCP has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 25 GitHub stars. World Monitor has 52/100 (Good) with 5 views, 0 installs and 89,438 GitHub stars.