A side-by-side look at the Last9 MCP Server and Observability MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Last9 MCP Server for monitoring work as a local process; choose Observability MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
LAST9_REFRESH_TOKEN.start_time_iso, end_time_iso, time_iso.list_sources, list_services, query_metrics.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 65/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | LAST9_REFRESH_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 62 | 7 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 80 | 8 |
| Full listing | View Last9 MCP Server | View Observability MCP |
start_time_isoend_time_isotime_isolookback_minuteslimitservice_namespan_nameenvsort_byrequest_countthroughput_rpmhttp_4xx_countlist_sourcesDiscover configured backends and connection statuslist_servicesDiscover monitored services across all backendsquery_metricsQuery metrics with pre-computed summary statsquery_logsQuery logs with error/warning counts and top patternsget_service_healthHealth score combining metrics + logs (0–100)detect_anomaliesCross-signal anomaly detection with robust (median/MAD + trend) analysisget_topologyReturn the merged infrastructure graph (resources + edges) from every topology-capable connector, filterable by source/kind/scopeget_blast_radiusPivot on the universal `RUNS_ON` relation — "if this resource's host fails, who else fails?". Works for pod→node, vm→hypervisor, container→hostPaste 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": {
"last9-last9-mcp-server": {
"command": "npx",
"args": [
"-y",
"@last9/mcp-server@latest"
],
"env": {
"LAST9_REFRESH_TOKEN": "YOUR_LAST9_REFRESH_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"observability-mcp": {
"command": "npx",
"args": [
"-y",
"@thotischner/observability-mcp"
]
}
}
}