OneUptime vs Bugsnag MCP
A side-by-side look at the OneUptime and Bugsnag MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OneUptime 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?
Choose OneUptime when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_team, get_team, list_teams.
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 | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 70/100 · Great | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | BUGSNAG_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7,757 | 25 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 199 | Not listed |
| Full listing | View OneUptime | View Bugsnag MCP |
Tools & capabilities
OneUptime tools 199
create_teamCreate a new Team in OneUptime. Returns the created Team object with its ID. Use this to add new Teams to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_teamRetrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID.list_teamsList and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count.update_teamUpdate an existing Team in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_team afterwards to see the updated record.delete_teamPermanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_teamsCount the total number of Teams in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.create_labelCreate a new Label in OneUptime. Returns the created Label object with its ID. Use this to add new Labels to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_labelRetrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID.list_labelsList and search Labels from OneUptime with optional filtering, pagination, and sorting. Returns an array of Label objects plus the total matching count.update_labelUpdate an existing Label in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_label afterwards to see the updated record.delete_labelPermanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_labelsCount the total number of Labels in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.- +187 more on 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.
OneUptime
{
"mcpServers": {
"oneuptime": {
"command": "npx",
"args": [
"-y",
"oneuptime"
]
}
}
}
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
OneUptime is categorized under Monitoring and uses a remote HTTP/SSE transport. Bugsnag MCP belongs to Monitoring and uses a local stdio subprocess. Pick OneUptime 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.
OneUptime has no declared pricing — check the project's own site. 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 oneuptime and tgeselle-bugsnag-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OneUptime has a quality signal of 70/100 (Great) with 2 views, 0 installs and 7,757 GitHub stars. Bugsnag MCP has 41/100 (Fair) with 0 views, 0 installs and 25 GitHub stars.