Awslabs MCP vs Radar

A side-by-side look at the Awslabs MCP and Radar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Awslabs MCP logoAwslabs MCPCloud Platforms · Local subprocess (stdio)AWS MCP servers for seamless integration with AWS services and resources.48FairAuth: api key requiredRadar logoRadarCloud PlatformsBuilt-in MCP server for Radar, a modern Kubernetes visibility tool. Lets AI agents query cluster topology, resources, events, logs, and Helm/GitOps state across multiple clusters. Single binary, no agents, no cloud dependency. Apache 2.0.55GoodAuth: no auth required

Verdict: choose Awslabs MCP for cloud platforms work as a local process; choose Radar for cloud platforms. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Awslabs MCP logoChoose Awslabs MCP when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Awslabs MCP

Radar logoChoose Radar when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • Its auth model fits you: No auth required.
Explore Radar

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAwslabs MCP logoAwslabs MCPRadar logoRadar
CategoryCloud PlatformsCloud Platforms
Quality signal48/100 · Fair55/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars9,8213,903
Directory activity 2 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Awslabs 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.

Awslabs MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "awslabs-mcp": {
      "command": "uvx",
      "args": [
        "awslabs.aws-api-mcp-server@latest"
      ]
    }
  }
}

Radar

No confirmed install command for Radar yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Awslabs MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Radar belongs to Cloud Platforms and uses an install path we have not confirmed yet. Pick Awslabs 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. Radar has no confirmed install command yet — follow its own setup instructions.

Awslabs MCP is listed as free. Auth: api key required. 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 awslabs-mcp and skyhook-io-radar as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Awslabs MCP has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 9,821 GitHub stars. Radar has 55/100 (Good) with 5 views, 0 installs and 3,903 GitHub stars.