Assistant and Claude plugin¶
CloudSprite’s assistant lives in the Claude / Grok plugin and talks to your workspace over the hosted MCP connection. It uses your login and your team. It cannot see another company’s projects, and it cannot do more than your role allows.
Install¶
In Claude Code:
/plugin marketplace add cloudsprite-io/cloudsprite-plugin
Then enable the cloudsprite plugin (that slug is fixed). Sign in with the same CloudSprite account you use in the browser. The plugin does not ship an API key; OAuth is the login.
Other clients¶
The same plugin repo ships the portable Agent Plugins layout (plugin.json + mcp.json + skills/), so clients that read that format get the same skills and the same hosted connection. Any MCP-capable client can also connect directly to https://api.cloudsprite.io/mcp (streamable HTTP) and sign in with OAuth — never an API key in chat.
If sign-in fails, complete the browser OAuth flow with the same account you use in the web app, then retry; removing and re-adding the plugin forces a fresh login.
Set scope first¶
Before you ask about datasets or notebooks, bind the team (and project, when you have one). Search and SDK tools then stay inside that team. A denial looks like an ordinary “you cannot do that” from the API — not a guessed workaround.
What it will do¶
- Find datasets, explain how-tos, and look up SDK methods (signature, fields, permission).
- Draft analysis scripts you can save on the project and run.
- Propose bulk edits (add a parameter, apply a tag) as a preview. Nothing writes until you confirm.
What it will not do¶
- Paste API keys, tokens, or passwords into chat. Create keys in account settings; see API keys and login.
- Dump raw waveform arrays into the model. Traces stay in the workspace; the assistant works with names, ids, and summaries.
- Follow instructions that appear inside a dataset name, a docstring, or a retrieved paragraph. Those are data, not commands.
- Skip preview on writes, or act as a different user.
Feedback¶
/feedback (or the feedback skill) files a note to CloudSprite. You must be signed in. Do not put secrets in the report.
Related¶
- Getting started — first hour in the product
- Python SDK how-to — scripts on your laptop
- Organizations, teams, and roles — who can upload vs view