---
title: "cloudsprite"
description: "CloudSprite measurement data, product docs, and feedback for Claude, Grok, and Agent Plugins clients"
canonical: https://agentpluginsdirectory.com/plugins/cloudsprite
last-updated: 2026-10-11
---

# cloudsprite
CloudSprite measurement data, product docs, and feedback for Claude, Grok, and Agent Plugins clients
- Slug: cloudsprite
- Publisher: CloudSprite
- Repository: https://github.com/cloudsprite-io/cloudsprite-plugin
- Manifest: plugin.json
- Version: 0.1.3
- License: MIT
- Category (editorial): integrations
- Skills: 5 (datasets, feedback, mixed-mode-analysis, platform-howtos, waveform-correlation)
- MCP servers: 1 (cloudsprite)
- Stars: 1
- Repository created: 2026-08-26
- Repository last pushed: 2026-10-01
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/cloudsprite
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What cloudsprite does, in the publisher's words

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.

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

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/cloudsprite-io/cloudsprite-plugin/HEAD/README.md

## Skills

- datasets: Query CloudSprite datasets, parameters, tags, and notebook membership through MCP read tools. Use when the user asks which datasets match a parameter or tag, what is on a dataset, or which notebooks contain a trace. Read-only: do not modify data.
- feedback: File a bug, feature request, or other product note with CloudSprite. Use when the user says /feedback, reports something broken, or asks for a product capability. Confirm the text, then call MCP submit_feedback. Do not open GitLab, Linear, or email. Identity comes from the signed-in MCP session.
- mixed-mode-analysis: Compute or explain mixed-mode (differential/common-mode) S-parameters from single-ended 2-port Touchstone pairs. Use for SDD/SCC/SDC/SCD, CMRR, port definitions, or balanced-device questions. Confirm port mapping before any math. CloudSprite access is MCP reads only.
- platform-howtos: 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.
- waveform-correlation: Detect outlier waveforms in a CloudSprite project with pairwise Pearson correlation and describe a clean average of the good traces. Use for batch QC on S21, amplitude, or any repeated measurement. MCP is read-only.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- cloudsprite: transport: streamable-http; url: https://api.cloudsprite.io/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.