Sentry MCP vs RadioChron
A side-by-side look at the Sentry MCP and RadioChron MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sentry MCP for monitoring work as a local process; choose RadioChron 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 Sentry MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SENTRY_ACCESS_TOKEN, EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, OPENROUTER_MODEL, OPENROUTER_REASONING_EFFORT, SENTRY_HOST.
Choose RadioChron when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RADIOCHRON_CHRONICLE_PATH. - You want tools like
diagnose_incident, wifi_status, wifi_networks.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 55/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | SENTRY_ACCESS_TOKENEMBEDDED_AGENT_PROVIDEROPENAI_API_KEYANTHROPIC_API_KEYOPENROUTER_API_KEYOPENROUTER_MODELOPENROUTER_REASONING_EFFORTSENTRY_HOST | RADIOCHRON_CHRONICLE_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 938 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 17 |
| Full listing | View Sentry MCP | View RadioChron |
Tools & capabilities
Sentry MCP tools
No tool names declared yet. Check the project README from the listing page.
RadioChron tools 17
diagnose_incidentOrchestrate Wi-Fi, connectivity, history, chronicle, and optional native BLE evidence in one compact responsewifi_statusCurrent state of every WLAN interfacewifi_networksNearby BSS records with real dBm, security, width, and load; summary or full detailwifi_analyzeSignal, contention, roaming, security, and scan-quality findingswifi_sampleCancelable RSSI/rate/roaming sampling with progresswifi_scanNative Wi-Fi refresh with per-interface completion/failureconnectivity_diagnoseSeparate radio, authentication, IP assignment, gateway, DNS, TCP, portal, TLS, quality, and Internet stageschronicle_startStart the local rotating change-only JSONL recorderchronicle_stopStop and flush the recorderchronicle_statusRecorder state, path, counters, and latest errorchronicle_recentRecent entries from active and rotated filesble_scanScan native adapters without connecting, normalize advertisements, update histories, and return risk evidence- +5 more on 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.
Sentry MCP
{
"mcpServers": {
"getsentry-sentry-mcp": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_ACCESS_TOKEN": "YOUR_SENTRY_ACCESS_TOKEN_HERE",
"EMBEDDED_AGENT_PROVIDER": "YOUR_EMBEDDED_AGENT_PROVIDER_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"OPENROUTER_MODEL": "YOUR_OPENROUTER_MODEL_HERE",
"OPENROUTER_REASONING_EFFORT": "YOUR_OPENROUTER_REASONING_EFFORT_HERE",
"SENTRY_HOST": "YOUR_SENTRY_HOST_HERE"
}
}
}
}
RadioChron
{
"mcpServers": {
"radiochron": {
"command": "npx",
"args": [
"-y",
"radiochron-mcp"
],
"env": {
"RADIOCHRON_CHRONICLE_PATH": "YOUR_RADIOCHRON_CHRONICLE_PATH_HERE"
}
}
}
}
Frequently asked questions
Sentry MCP is categorized under Monitoring and uses a local stdio subprocess. RadioChron belongs to Monitoring and uses a local stdio subprocess. Pick Sentry MCP for monitoring work and RadioChron 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.
Sentry MCP is listed as free. Auth: api key required. RadioChron 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 getsentry-sentry-mcp and radiochron as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sentry MCP has a quality signal of 55/100 (Good) with 6 views, 0 installs and 938 GitHub stars. RadioChron has 53/100 (Good) with 2 views, 0 installs and 1 GitHub stars.