In-depth architectural comparison of the Cloud Cost MCP and MCP Server Aws Sso MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Cloud Cost MCP
Cloud Platforms · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
MCP Server Aws Sso
Cloud Platforms · Local stdio
Quality: 63/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Cloud Cost MCP if you need specialized Cloud Platforms tools running via a local process. Choose MCP Server Aws Sso if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cloud Cost MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Multi-cloud pricing comparison across AWS, Azure, GCP, and OCI with 2,700+ instance types. Real-time pricing from public APIs, workload calculators, and migration savings estimator.
AWS Single Sign-On (SSO) integration enabling AI systems to securely interact with AWS resources by initiating SSO login, listing accounts/roles, and executing AWS CLI commands using temporary credentials.
Category & Scope
Tools & Capabilities Breakdown
Cloud Cost MCP Tools (31)
compare_compute
Compare VM/instance pricing across AWS, Azure, GCP, and OCI. Finds instances matching your vCPU and memory requirements.
compare_storage
Compare object and block storage pricing across all clouds.
compare_egress
Compare data transfer/egress costs. OCI offers 10TB/month free (100x more than others)!
compare_kubernetes
Compare managed Kubernetes pricing (EKS, AKS, GKE, OKE). Shows control plane and worker node costs.
find_cheapest_compute
Find the cheapest cloud provider for specific compute specs.
calculate_workload_cost
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Cloud Cost MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, MCP Server Aws Sso belongs to Cloud Platforms using local stdio subprocess. Select Cloud Cost MCP when you need capabilities focused on cloud platforms and MCP Server Aws Sso when you require tools for cloud platforms.
Estimate total monthly cost for a workload across all cloud providers. Includes compute, storage, egress, and Kubernetes.
quick_estimate
Get instant cost comparison for common deployment presets including GPU workloads.
list_presets
List all available deployment presets for quick_estimate.
estimate_migration_savings
Calculate potential savings when migrating from one cloud provider to another.
get_data_freshness
Check how recent the pricing data is for each provider. Warns if data is stale (>30 days).
get_provider_details
Get detailed pricing data for a specific cloud provider.
get_storage_summary
Get storage pricing summary by tier (hot, cool, cold, archive) for all providers.
+19 more tools listed on main page
MCP Server Aws Sso Tools (5)
aws_sso_login
Initiate AWS SSO device authorization flow to obtain temporary credentials.
This flow works as follows:
1. Generates a unique user verification code and authentication URL
2. Opens a browser to AWS SSO login page (if `launchBrowser: true`)
3. You enter the verification code and complete AWS SSO login
4. Background polling automatically collects and caches the token
5. The cached token is used by other AWS SSO tools
**IMPORTANT FOR AI ASSISTANTS**: When the tool returns authentication instructions:
- ALWAYS check if a browser window opened automatically
- If browser opened: Guide the user to complete authentication
- If no browser opened: Instruct user to manually open the URL and enter code
- Always provide both the verification code and URL as backup
Prerequisites:
- AWS SSO must be configured with a start URL and region
- Browser access is required for authentication
- You must have an AWS SSO account with appropriate permissions
Returns: Authentication status, session details, verification code and URL
aws_sso_status
Check current AWS SSO authentication status.
Verifies if a valid cached token exists and its expiration time. Does NOT perform authentication - only checks status. If no valid token exists, instructs you to run `aws_sso_login`.
Use before calling `aws_sso_ls_accounts` or `aws_sso_exec_command`.
Returns: Authentication status, session details, expiration time, next steps
aws_sso_ls_accounts
List all AWS accounts and roles accessible through AWS SSO.
Provides essential information needed for `aws_sso_exec_command`:
- Fetches all accessible accounts with IDs, names, and emails
- Retrieves all available roles for each account
- Handles pagination internally
- Caches account and role information
Prerequisites:
- MUST first authenticate using `aws_sso_login`
- AWS SSO must be configured with a start URL and region
Returns: Account list with IDs, names, roles, and session status
aws_sso_exec_command
Execute AWS CLI command using temporary credentials from AWS SSO.
Workflow:
1. Verifies valid AWS SSO authentication token
2. Obtains temporary credentials for account and role
3. Executes the AWS CLI command
4. Caches credentials for future use (1 hour)
Prerequisites:
- MUST first authenticate using `aws_sso_login`
- AWS CLI MUST be installed on the system
- AWS SSO must be configured
Required: `accountId`, `roleName`, `command`
Optional: `region`
Returns: Execution context, command output, errors, exit code
aws_sso_ec2_exec_command
Execute shell command on EC2 instance via SSM using AWS SSO credentials.
No SSH access or inbound ports required. Uses SSM's RunShellScript document.
Prerequisites:
- MUST first authenticate using `aws_sso_login`
- EC2 instance MUST have SSM Agent installed
- Instance needs IAM role with AmazonSSMManagedInstanceCore policy
- Your role needs `ssm:SendCommand` and `ssm:GetCommandInvocation` permissions
Required: `instanceId`, `accountId`, `roleName`, `command`
Optional: `region`
Returns: Execution context, command output, errors, troubleshooting guidance