CloudSprite

io.github.cloudsprite-ioPublished by GitHub account cloudsprite-iov0.1.3Updated Oct 24, 2026

Signed-in CloudSprite: search datasets and docs, set org/team/project scope, file feedback.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

CloudSprite's remote MCP server lets a signed-in assistant search datasets, traces, notebooks, scripts and product docs, set org/team/project scope, and file…

What you can do
  • Read org, team and project context and switch the active scope
  • Search datasets, traces (summaries only), notebooks and scripts
  • Search CloudSprite product docs and the SDK catalog
  • File a bug or feature request through the feedback tool
When to use it
Use it when you work inside CloudSprite and want an assistant to find datasets, notebooks or scripts, look up platform docs and SDK details, or submit a bug or feature request without leaving the chat.
Requirements
A remote MCP endpoint over Streamable HTTP, reached through OAuth sign-in with the same CloudSprite account used in the browser. No API key or client secret is configured; the client discovers the authorization and token endpoints from the server's metadata and holds the tokens. A client that supports remote MCP with OAuth is needed.
Before you install
Sign-in grants the assistant access to your CloudSprite org, team and project data, so scope it deliberately. The feedback tool sends text to CloudSprite, which files it in its own tracker. The release is described as read-only apart from feedback, but confirm that before relying on it. ChatGPT custom connectors are not yet supported.

Installation

In SourceWeft

  1. Open CloudSprite in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.cloudsprite-io%2Fcloudsprite/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

CloudSprite plugin

Public plugin for CloudSprite. One repo, one plugin slug (cloudsprite), for Claude Code, Grok Build, and Agent Plugins clients (Cursor, GitHub Copilot, VS Code, Codex, and others).

The plugin talks to production CloudSprite over remote MCP. There are no API keys, GitLab tokens, Linear tokens, or other secrets in this repository. OAuth tokens stay in the client.

Plugin name is cloudsprite and is immutable once a marketplace lists it. The GitHub org is cloudsprite-io because cloudsprite was already taken on GitHub.

Connect your AI to CloudSprite

Full per-client steps: Connect your AI to CloudSprite.

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

WhatValue
MCP URLhttps://api.cloudsprite.io/mcp
TransportStreamable HTTP
OAuth discoveryhttps://api.cloudsprite.io/.well-known/oauth-authorization-server
Plugin slugcloudsprite (fixed)

How do I connect Claude Code to CloudSprite?

text
/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.

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

This repo is an Agent Plugins 1.0 package: root plugin.json, mcp.json, and skills/.

  1. Clone this repository (or add cloudsprite-io/cloudsprite-plugin 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 a remote MCP server instead (same URL and OAuth as any MCP client).

How do I connect Grok to CloudSprite?

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

Official listing on xAI’s marketplace is separate and not required for this install. Maintainer catalog notes: DIRECTORY.md.

How do I connect any MCP client to CloudSprite?

SettingValue
Server URLhttps://api.cloudsprite.io/mcp
TransportStreamable HTTP
OAuth discoveryhttps://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.

json
{  "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.

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.

What it does

After you sign in and set scope, the model can:

  • Read org / team / project context (whoami / get_scope, list_orgs, list_teams, list_projects, set_scope)
  • Search datasets, traces (summaries only), notebooks, and scripts
  • Search CloudSprite product docs and the SDK catalog (search_knowledge, search_sdk)
  • File a bug or feature request (/feedback → MCP submit_feedback)

This release is read-only plus feedback. It does not mutate datasets, tags, notebooks, or scripts.

MCP URL

Production (the only URL customers use):

text
https://api.cloudsprite.io/mcp

Transport: MCP Streamable HTTP. No Authorization header is stored in the plugin. The client discovers OAuth from the MCP origin and holds the tokens. There is no environment picker in the plugin UI.

A 401 from /mcp before OAuth is live is expected. The plugin should fail with a clear auth error, not hang.

Claude Code honors CLOUDSPRITE_MCP_URL if the client process has it set (${CLOUDSPRITE_MCP_URL:-https://api.cloudsprite.io/mcp} in .mcp.json). The GUI app reads ~/.claude/settings.json "env", not your shell profile. Portable mcp.json is a literal production URL (no interpolation). Do not commit a .env here.

Skills

| Skill | Slash | Purpose | |-|-| | feedback | /feedback | Confirm text, then call MCP submit_feedback | | platform-howtos | /platform-howtos | Sign-in, scope, and how to use CloudSprite from the assistant | | datasets | /datasets | Find datasets, parameters, tags, and notebooks (read) | | mixed-mode-analysis | /mixed-mode-analysis | Differential / common-mode S-parameters from 2-port pairs | | waveform-correlation | /waveform-correlation | Pairwise Pearson QC across repeated traces |

Network endpoints

The plugin package does not open sockets itself. Clients that load it will contact:

URLWhy
https://api.cloudsprite.io/mcpMCP Streamable HTTP (tools)
https://api.cloudsprite.io/.well-known/oauth-authorization-serverOAuth 2.1 authorization-server metadata
https://api.cloudsprite.io/.well-known/oauth-protected-resourceOAuth protected-resource metadata (if advertised)
Authorization, token, revocation, and JWKS URLs from that metadataCognito Hosted UI PKCE. Hosts are not hardcoded here; they come from discovery.

Installing the plugin also clones this GitHub repository (https://github.com/cloudsprite-io/cloudsprite-plugin). Tagged releases are vMAJOR.MINOR.PATCH matching plugin.json version.

The plugin does not call GitLab, Linear, HubSpot, or any issue tracker. Feedback is filed by the CloudSprite API after submit_feedback.

If CLOUDSPRITE_MCP_URL is set, discovery and token endpoints follow that host instead of api.cloudsprite.io.

Support

Releases

Git tags are v + the version in plugin.json (currently 0.1.3). Maintainers publish with scripts/publish.sh after scripts/audit.sh passes. Republishing the same tag is a no-op if HEAD still matches; a different tree at the same version fails.

License

MIT. Copyright © 2026 Brushfield Ventures LLC d/b/a CloudSprite.

Product use of CloudSprite remains under the CloudSprite Terms of Service and Privacy Policy.

Source: README.md at commit da149c1

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts