Sprite MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the server listens on (default is 3847). | 3847 |
| SPRITE_BIN | No | The path to the sprite binary (usually ~/.local/bin/sprite). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_spritesC | List all available Sprite VMs in the organization. Returns an interactive dashboard to manage sprites. |
| exec_commandC | Execute a command on a remote Sprite VM |
| create_checkpointB | Create a filesystem checkpoint/snapshot of a Sprite VM for quick restore |
| list_checkpointsC | List all checkpoints for a Sprite VM |
| restore_checkpointC | Restore a Sprite VM to a previous checkpoint state |
| get_sprite_urlB | Get the public URL for a Sprite VM |
| fetch_fileA | Download a file from a remote Sprite VM to the local filesystem |
| push_fileC | Upload a file from local filesystem to a remote Sprite VM |
| list_sessionsC | List active sessions on a Sprite VM |
| create_spriteC | Create a new Sprite VM |
| destroy_spriteA | Destroy/delete a Sprite VM (requires confirmation) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Sprite Dashboard | Interactive dashboard for managing Sprite VMs |
| Sprite Terminal | Interactive terminal for executing commands on Sprite VMs |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, create_sprite, destroy_sprite, and list_sprites handle VM lifecycle management, while fetch_file and push_file handle file transfers, and checkpoint tools manage snapshots. The descriptions clearly differentiate each tool's specific function.
All tools follow a consistent verb_noun naming pattern throughout (e.g., create_checkpoint, list_sessions, push_file). There are no deviations in style or convention, making the tool set predictable and easy to understand.
With 11 tools, this is well-scoped for managing Sprite VMs. Each tool earns its place by covering essential operations like VM lifecycle, file management, checkpointing, and session monitoring without being excessive or insufficient.
The tool surface provides complete coverage for the Sprite VM domain, including CRUD operations (create, list, destroy), file management (push, fetch), checkpoint lifecycle (create, list, restore), and additional utilities (exec_command, get_sprite_url, list_sessions). There are no obvious gaps that would hinder agent workflows.