Sprite MCP Server
Enables management of Sprite VMs through interactive dashboards and terminal interfaces. It allows users to execute commands, create filesystem snapshots, transfer files, and manage VM lifecycles via natural language.
README
Sprite MCP Server
MCP server for managing Sprite VMs with interactive UI dashboards (MCP Apps).
Works with Claude.ai, Claude Desktop, Claude Code, VS Code, and any MCP-compatible client.
Features
- List & manage Sprite VMs - Interactive dashboard with status indicators
- Execute commands - Terminal UI with command history
- Checkpoints - Create, list, restore filesystem snapshots
- File transfer - Push/pull files to/from remote sprites
- Session management - List, attach, kill sessions
Quick Deploy to Your Server
Prerequisites
- Node.js 20+
- A domain pointing to your server (for HTTPS)
- Sprite CLI configured with credentials
1. Clone & Install
git clone https://github.com/davidkiama/sprite-mcp-server.git
cd sprite-mcp-server
npm install
npm run build
2. Configure Environment
cp .env.example .env
# Edit .env with your settings
PORT=3847
SPRITE_BIN=/path/to/sprite # Usually ~/.local/bin/sprite
3. Run with systemd (Recommended)
# Copy service file
sudo cp sprite-mcp.service /etc/systemd/system/
# Edit the service file to set your paths
sudo nano /etc/systemd/system/sprite-mcp.service
# Enable and start
sudo systemctl daemon-reload
sudo systemctl enable sprite-mcp
sudo systemctl start sprite-mcp
# Check status
sudo systemctl status sprite-mcp
4. Set Up Reverse Proxy (Caddy)
# Install Caddy if needed
sudo apt install -y caddy
# Add to /etc/caddy/Caddyfile
echo '
mcp.yourdomain.com {
reverse_proxy localhost:3847
}
' | sudo tee -a /etc/caddy/Caddyfile
# Reload Caddy
sudo systemctl reload caddy
5. Connect to Claude.ai
- Go to claude.ai/settings/integrations
- Add MCP Server:
- Name:
sprite-mcp - URL:
https://mcp.yourdomain.com/sse
- Name:
- Test by asking Claude: "List my sprites"
Local Development
# Run stdio server (for Claude Code/Desktop)
npm start
# Run HTTP/SSE server (for claude.ai)
npm run start:http
# Development mode with hot reload
npm run dev
MCP Tools
| Tool | Description |
|---|---|
list_sprites |
List all Sprite VMs (with interactive dashboard) |
exec_command |
Execute command on a sprite (with terminal UI) |
create_checkpoint |
Create filesystem snapshot |
list_checkpoints |
List available checkpoints |
restore_checkpoint |
Restore to a checkpoint |
get_sprite_url |
Get sprite's public URL |
fetch_file |
Download file from sprite |
push_file |
Upload file to sprite |
list_sessions |
List active sessions |
create_sprite |
Create new sprite VM |
destroy_sprite |
Delete a sprite VM |
Interactive UIs (MCP Apps)
This server uses MCP Apps to provide interactive interfaces:
- Dashboard (
ui://sprite/dashboard) - Visual sprite management - Terminal (
ui://sprite/terminal) - Command execution interface
These render directly in the Claude conversation when using supported clients.
Architecture
┌─────────────────────────────────────────────────────────┐
│ Claude.ai / Desktop │
├─────────────────────────────────────────────────────────┤
│ MCP Protocol │
│ (stdio or HTTP/SSE transport) │
├─────────────────────────────────────────────────────────┤
│ sprite-mcp-server │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────────┐ │
│ │ MCP Tools │ │ UI Resources│ │ Sprite CLI │ │
│ │ (11 tools) │ │ (Dashboard) │ │ Integration │ │
│ └─────────────┘ └─────────────┘ └─────────────────┘ │
├─────────────────────────────────────────────────────────┤
│ Sprite CLI │
│ (sprite list, exec, checkpoint...) │
├─────────────────────────────────────────────────────────┤
│ Sprites API / VMs │
└─────────────────────────────────────────────────────────┘
Troubleshooting
Check if server is running
curl http://localhost:3847/health
# Should return: {"status":"ok","server":"sprite-mcp","version":"1.0.0"}
Check logs
# If using systemd
journalctl -u sprite-mcp -f
# If running directly
npm run start:http 2>&1 | tee mcp.log
Test MCP handshake
echo '{"jsonrpc":"2.0","method":"tools/list","params":{},"id":1}' | npm start
Sprite CLI not found
# Find sprite binary
which sprite
# Set in .env
SPRITE_BIN=$(which sprite)
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.