🤔 What is happening
When using the Search Atlas MCP or API, cs_list returns all cloud stacks for the currently selected OTTO project. If you have cloud stacks in Project A but your dashboard is set to Project B, cs_list returns Project B's stacks — which may show 0 deployed providers.
Meanwhile, cs_get fetches a specific stack by ID regardless of the active project — so it correctly shows your active providers.
✅ This is not a bug
The discrepancy between cs_list and cs_get is a project selection mismatch, not a data error. Your stacks and providers are intact.
🛠️ How to fix it
- In your Search Atlas dashboard, check which OTTO project is currently active in the project selector
- Switch to the correct OTTO project that contains your cloud stacks
- Re-run
cs_list— it should now return the correct stacks
🔌 If you are using the MCP or API
When calling cs_list via the MCP server or REST API, pass the project_id parameter explicitly if available, or verify your session is authenticated to the correct project context.
🚨 If switching projects doesn't fix it
If you have confirmed the correct OTTO project is active and a provider still shows as not deployed, the deployment itself may have failed rather than the data being missing. Cloud Stack provider calls do not currently retry automatically, so a single network interruption during deployment can cause that provider to fail permanently (Linear AB-547, status: Canceled — an automatic retry with exponential backoff was proposed but not implemented). In that case, re-deploy the affected provider.
Separately, if the Cloud Stack AI agent suggested fewer providers than you expected, this was a known issue where the agent's prompt wording anchored on a fixed count (~14–15) instead of the live provider list (Linear AIAGENT-2101, status: Done — now resolved). Cloud Stacking supports 40+ publishing destinations, including REST API providers such as Netlify, Neocities, Firebase, and Tiiny Host.