Skip to content

Integrations

Sprites can be used through the hosted MCP server, a client plugin, an SDK adapter, or a platform’s sandbox backend. Choose the path that matches where your agent already runs.

These plugins connect a coding agent to Sprites. Most use the hosted MCP server and browser OAuth; Pi uses a Sprites API token, while Herdr uses the authenticated Sprites CLI.

IntegrationConnectionSetup
CodexPlugin + hosted MCPAgent plugins
CursorMarketplace plugin + hosted MCPAgent plugins
AntigravityGit-installed plugin + hosted MCPAgent plugins
Grok BuildGit-installed plugin + hosted MCPAgent plugins
Cortex CodeGit-installed plugin + hosted MCPCortex Code guide
DeepSeek HarnessGitHub bundle + local OAuth bridgeAgent plugins
OpenCodeSource-installed plugin + hosted MCPAgent plugins
PiGit-installed extension + Sprites APIAgent plugins
HerdrAgent pane plugin + Sprites CLIAgent plugins

Use these adapters when your application owns the agent loop and needs to create or reuse Sprites programmatically.

IntegrationLanguageSetup
Hugging Face OpenEnvPythonSDKs and frameworks
Google Agent Development Kit (ADK)PythonSDKs and frameworks
OpenAI Agents SDKPythonSDKs and frameworks
OpenRouter Agent SDKTypeScriptSDKs and frameworks
TanStack AITypeScriptSDKs and frameworks
IntegrationWhat it providesSetup
Anthropic Connectors DirectoryA hosted Sprites connector for ClaudePlatform integrations
Claude Managed AgentsA self-hosted sandbox worker backed by SpritesClaude Managed Agents guide
Mistral AIMCP connector setup reference for Mistral StudioRemote MCP Server
QM by Y CombinatorA Sprites sandbox backend in a QM deploymentPlatform integrations

The Sprites remote MCP server is published as dev.sprites/mcp in the official MCP registry and has a Smithery listing.

See Registry and discovery for listing links and the differences between their connection flows.