Adiosdotdev MCP vs Radar
A side-by-side look at the Adiosdotdev MCP and Radar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Adiosdotdev MCPCloud Platforms · Local subprocess (stdio)Manage Adios workspaces, previews, builds, logs, services and production deployments.43FairAuth: oauth 2.0Verdict: choose Adiosdotdev MCP for cloud platforms work as a local process; choose Radar for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Adiosdotdev MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Choose Radar when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Adiosdotdev MCP | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 43/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 3,823 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Adiosdotdev MCP | View Radar |
Tools & capabilities
Adiosdotdev MCP tools
No tool names declared yet. Check the project README from the listing page.
Radar 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.
Adiosdotdev MCP
{
"mcpServers": {
"adiosdotdev-mcp": {
"command": "npx",
"args": [
"-y",
"@adiosdotdev/mcp"
]
}
}
}
Radar
{
"mcpServers": {
"skyhook-io-radar": {
"url": "https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=1130618&theme=neutral&period=daily"
}
}
}
Frequently asked questions
Adiosdotdev MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Radar belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Adiosdotdev MCP for cloud platforms work and Radar for cloud platforms.
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.
Adiosdotdev MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. Radar is listed as free. Auth: no auth required. 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 adiosdotdev-mcp and skyhook-io-radar as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Adiosdotdev MCP has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Radar has 60/100 (Good) with 4 views, 0 installs and 3,823 GitHub stars.