← ClaudeAtlas

platform-howtoslisted

How to use CloudSprite from this plugin: sign in, set org/team/project scope, search datasets and product docs, and file feedback. Use when the user is new to the plugin, asks how CloudSprite works, or hits auth/scope errors.
cloudsprite-io/cloudsprite-plugin · ★ 1 · API & Backend · score 67
Install: claude install-skill cloudsprite-io/cloudsprite-plugin
# CloudSprite from the assistant This plugin is the customer assistant for CloudSprite. You act as the **signed-in user**. Tools run with their permissions. You never get a CloudSprite API key from this repo. ## 1. Sign in The MCP server is `https://api.cloudsprite.io/mcp` (Streamable HTTP). Customers do not configure this URL. Do not mention other environments. The client runs OAuth 2.1 with PKCE. Authorization-server metadata is discovered from the MCP URL (`/.well-known/oauth-authorization-server`). Tokens stay in the client. If tools fail with **401** or "unauthorized": - Ask the user to complete CloudSprite sign-in in the client. - Do not collect passwords or paste tokens into chat. - MCP may not be publicly live yet. Say so if the server is unreachable or the tool list is empty. ## 2. Set scope CloudSprite data is org → team → project. Bind scope before searching. Typical order: 1. `whoami` or `get_scope` — see the current user and bound org/team/project 2. `list_orgs` / `list_teams` / `list_projects` — only what they can see 3. `set_scope` — org, team, and project the rest of the session should use If a tool returns a permission error, relay it. Do not retry against another tenant. ## 3. Find measurement data Use MCP **read** tools only: | Ask | Tool | |-|-| | Which datasets match a name, parameter, or tag? | `search_datasets` | | Parameters, tags, traces, provenance for one dataset | `get_dataset` | | Trace shape (range, points, min/max/mean) | `get_tr