- Home
- Top MCPs for Cloud & Infrastructure
- AWS vs Grafana
MCP Comparison · 2026
AWS vs Grafana MCP Server
Comparing AWS and Grafana as MCP servers? AWS (inspect aws) is best when incident investigation. Grafana (query grafana dashboards) is best when incident investigation across metrics + logs. Both run as Model Context Protocol servers and can coexist in the same client. Updated 2026.
Side-by-side specs
Pulled from each MCP's verified fact sheet.
| AWS | Grafana | |
|---|---|---|
| Primary function | Inspect AWS | Query Grafana dashboards |
| Maintainer | AWS | Grafana Labs |
| Pricing | Freemium | Freemium |
| Setup complexity | Medium · ~10 min | Medium · ~5 min |
| Transport | Streamable HTTP | stdio, SSE, Streamable HTTP |
| Auth model | OAuth 2.1 | API key |
| License | Proprietary | Apache-2.0 |
| Language | — | Go |
| Latest version | remote | latest |
| Compatible clients | Claude, Claude Code, Cursor, Codex, Kiro, Gemini CLI, Any remote-MCP client with OAuth | Claude, Cursor, VS Code, Any MCP-compatible client, Grafana 9.0+ |
| Last verified | 2026-09-05 | 2026-10-01 |
Which one should you pick?
Decision rubric drawn from each MCP's documented strengths.
Choose AWS
- Incident investigation
- IAM and security audits
- Multi-step resource queries in one script call
Choose Grafana
- Incident investigation across metrics + logs
- Querying Prometheus and Loki via one MCP
- Dashboard search and editing
Pick something else if…
- Provisioning new infrastructure
- Grafana versions before 9.0
Feature breakdown
Key capabilities each server ships out of the box.
AWS
- Managed by AWS — nothing to run locally on the OAuth path
- Two Regions: us-east-1 and eu-central-1
- aws___run_script executes sandboxed Python across many AWS calls in one invocation
- IAM authorisation with CloudTrail audit and CloudWatch agent-activity metrics
- OAuth 2.1 for web/desktop clients, SigV4 via mcp-proxy-for-aws-cli for terminal agents
Grafana
- Dashboards + 12 datasource types (Prometheus, Loki, ClickHouse, CloudWatch…)
- Alerting, Incident, OnCall, Sift tools
- stdio, SSE, and streamable-http transports
- Service-account token auth
- Official Grafana Labs, Apache-2.0, Go
Install snippets
Open the detail page for ready-to-paste config for every major client.
Install AWS
Setup snippets for Claude, Cursor, VS Code, Windsurf →
claude mcp add aws-mcp https://aws-mcp.us-east-1.api.aws/mcp --transport httpInstall Grafana
Setup snippets for Claude, Cursor, VS Code, Windsurf →
docker run --rm -i -e GRAFANA_URL -e GRAFANA_SERVICE_ACCOUNT_TOKEN grafana/mcp-grafana -t stdioFAQ
AWS vs Grafana: which MCP server should I use?
Pick AWS when incident investigation. Pick Grafana when incident investigation across metrics + logs. AWS is built for inspect aws, while Grafana focuses on query grafana dashboards.
Can I run both AWS and Grafana together?
Yes. MCP clients run each server as a separate process and surface every server's tools simultaneously, so you can install both and let your agent decide which to call. Be deliberate with auth scopes when stacking servers.
How fresh is this comparison?
Updated for 2026. AWS's last verification: 2026-09-05. Grafana's last verification: 2026-10-01. We refresh detail-page facts on every catalog rebuild.
More AWS comparisons
Browse all Cloud & Infrastructure MCPs? See the full ranked list →