MCP server does not use default profile marked with asterisk

[joshrotenberg]

Description

The MCP server fails with Cloud profile 'default' not found even when a default profile is configured and marked with * in redisctl profile list.

Steps to Reproduce

1. Configure a cloud profile: redisctl cloud profile add demo
2. Set it as default (shown with * in profile list)
3. Start MCP server and call cloud_subscriptions_list
4. Error: Cloud profile 'default' not found

Expected Behavior

The MCP server should use the same profile resolution logic as the CLI:

1. Check for explicitly passed profile parameter
2. Check for default_cloud / default_enterprise in config
3. Fall back to first profile of the matching type

Current Behavior

The MCP server calls config.resolve_cloud_profile(None) which should work, but appears to be looking for a profile literally named "default" instead of using the configured default.

Relevant Code

• crates/redisctl-mcp/src/cloud_tools.rs:19-21 - Profile resolution in CloudTools::new()
• crates/redisctl-config/src/config.rs:275-290 - resolve_cloud_profile() implementation

Environment

• Profile list shows: demo* (cloud) and re-test (enterprise)
• Config file: ~/Library/Application Support/com.redis.redisctl/config.toml

Workaround

None currently - the MCP server requires profiles to work.