mcp and aws-cost-explorer-mcp-server
These are ecosystem siblings—the official AWS MCP server provides broad AWS service integration while the cost explorer server is a specialized domain-specific extension that complements the official tooling by adding financial visibility capabilities.
About mcp
awslabs/mcp
Official MCP Servers for AWS
Provides specialized MCP servers for AWS services including documentation access, infrastructure-as-code tools (CloudFormation, Terraform), databases, AI/ML services, and cost management—designed to integrate with AI coding assistants (Kiro, Cline, Cursor, Windsurf) and Claude Desktop via stdio transport. Enables LLM applications to access AWS context and perform authenticated API operations, with support for both local execution and remote deployment via AWS Lambda handlers.
About aws-cost-explorer-mcp-server
aarora79/aws-cost-explorer-mcp-server
MCP server for understanding AWS spend
Exposes AWS Cost Explorer and Bedrock usage metrics through Claude via Model Control Protocol, enabling natural language queries about cloud spending across services, regions, and instance types. Supports both local stdio transport and remote HTTPS deployment on EC2, with cross-account role assumption for multi-account AWS environments. Integrates CloudWatch Logs for Bedrock model invocation analysis and works with Claude Desktop or LangGraph agents.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work