Skip to content

Connect your AI to CloudSprite

Point Claude Code, Cursor, GitHub Copilot, Codex, Grok, or any MCP client at CloudSprite. The assistant uses your login and your team. It cannot see another company’s projects.

There is no API key in the plugin and none in chat. Sign in with the same CloudSprite account you use in the browser.

What Value
Plugin github.com/cloudsprite-io/cloudsprite-plugin
Plugin slug cloudsprite (fixed)
MCP URL https://api.cloudsprite.io/mcp
Transport Streamable HTTP
Auth OAuth, discovered from the MCP origin

How do I connect Claude Code to CloudSprite?

In Claude Code:

/plugin marketplace add cloudsprite-io/cloudsprite-plugin
/plugin install cloudsprite@cloudsprite

Enable the cloudsprite plugin if it is not already on. On first tool use, complete the browser sign-in with your CloudSprite account.

How do I connect Cursor, GitHub Copilot, VS Code, or Codex to CloudSprite?

The public plugin is an Agent Plugins 1.0 package: root plugin.json, mcp.json (Streamable HTTP to production), and skills/.

  1. Clone cloudsprite-io/cloudsprite-plugin (or add that GitHub repo as the plugin source, if your client accepts a git URL).
  2. Load it as an Agent Plugin. In Cursor, a local checkout under ~/.cursor/plugins/local/cloudsprite is enough.
  3. Enable the plugin and complete OAuth when the client prompts.

If the client cannot load Agent Plugins, add CloudSprite as a remote MCP server instead — same URL and OAuth as any MCP client.

How do I connect Grok to CloudSprite?

In Grok Build, add this repository as a marketplace source, then install the plugin:

grok plugin marketplace add cloudsprite-io/cloudsprite-plugin
grok plugin install cloudsprite --trust

Complete the browser sign-in on first MCP use. Official directory listing on xAI’s marketplace is separate and not required for this install.

How do I connect any MCP client to CloudSprite?

Any client that speaks MCP Streamable HTTP and OAuth can skip the plugin and talk to production directly.

Setting Value
Server URL https://api.cloudsprite.io/mcp
Transport Streamable HTTP
OAuth discovery https://api.cloudsprite.io/.well-known/oauth-authorization-server

The client must discover authorization, token, and JWKS URLs from that metadata. Do not hard-code those hosts, and do not put a client secret or API key in the config. Example MCP config:

{
  "mcpServers": {
    "cloudsprite": {
      "type": "streamable-http",
      "url": "https://api.cloudsprite.io/mcp"
    }
  }
}

Some clients use "type": "http" or a bare "url" field for the same remote server. After connect, sign in with your CloudSprite account when the browser opens.

How do I connect ChatGPT to CloudSprite?

ChatGPT connectors are coming soon. Do not add CloudSprite as a ChatGPT custom connector yet — that OAuth redirect is not registered.

Use Claude Code, Cursor, Copilot, Codex, Grok, or a generic MCP client today.

After you connect

  1. Sign in with the same account you use in the web app.
  2. Bind the team (and project, when you have one) before you ask about datasets or notebooks. Search stays inside that team.
  3. A denial looks like an ordinary “you cannot do that” from the product — not a guessed workaround.

If sign-in fails, finish the browser OAuth flow, then retry. Removing and re-adding the plugin (or the MCP server) forces a fresh login.

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.

The current plugin release is read-only plus /feedback. It does not mutate datasets, tags, notebooks, or scripts. Product writes still go through preview then confirm.