Account persistence issue: set_active_account succeeds but other MCP tools report "No currently active accountId"

[sh0umik]

Bug Description

After successfully setting an active account using set_active_account, other MCP tools consistently report "No currently active accountId" despite the account setting appearing successful.

Environment

• OS: macOS 24.6.0
• IDE: Cursor with MCP integration
• Account ID: ed3b172a76f48c5ae3cffca0de8b9417
• MCP Servers: bindings, builds, docs (all connected)

Steps to Reproduce

1. Connect to Cloudflare MCP servers
2. Call set_active_account with valid account ID
3. Immediately call any non-Workers tool (e.g., r2_buckets_list, kv_namespaces_list, hyperdrive_configs_list)
4. Observe "No currently active accountId" error

Expected Behavior

All MCP tools should work after setting the active account.

Actual Behavior

• ✅ Workers MCP works perfectly - can list workers without issues
• ❌ Other MCPs fail consistently with "No currently active accountId"
• ❌ Account persistence doesn't work across different MCP services

Affected Tools

• r2_buckets_list
• kv_namespaces_list
• hyperdrive_configs_list
• list_gateways (AI Gateway)
• Any other non-Workers Cloudflare MCP tools

Workaround

Using wrangler CLI works reliably for all operations.

Additional Context

This suggests there might be a difference in how the Workers MCP handles account persistence compared to other MCP services. The issue persists across MCP server restarts and appears to be a systemic problem with account state management.

[sh0umik]

Additional Details for Account Persistence Issue

I'm experiencing the same issue described here. Here are additional details that might help with debugging:

Environment:

• macOS 24.6.0
• Cursor IDE with MCP integration
• Multiple Cloudflare MCP servers running: bindings, builds, docs
• Account ID: ed3b172a76f48c5ae3cffca0de8b9417

Specific Behavior:

1. Workers MCP works perfectly - can list workers without issues
2. Other MCPs fail consistently with "No currently active accountId":
   • R2 buckets (r2_buckets_list)
   • KV namespaces (kv_namespaces_list)
   • Hyperdrive configs (hyperdrive_configs_list)
   • AI Gateways (list_gateways)

Steps to Reproduce:

1. Set active account: set_active_account returns success
2. Immediately call any non-Workers tool (e.g., r2_buckets_list)
3. Get "No currently active accountId" error
4. Workers tools continue to work fine

Workaround:

Using wrangler CLI works reliably for all operations.

Additional Notes:

• The issue persists across MCP server restarts
• Account setting appears successful but doesn't persist to other tools
• Only Workers MCP maintains account state properly

This suggests there might be a difference in how the Workers MCP handles account persistence compared to other MCP services.