Skip to main content
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.
Some integrations are still source-only or in preview. Their guides call that out explicitly so you don’t try to install a package that has not been published.

Which guide should I use?

Agent clients and plugins

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

SDKs and frameworks

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

Platform integrations

MCP directories

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.