Cubelife runs on your own machine — the client starts it, so there is no endpoint to ping. 40 installs a week from npm. Last commit 4 Jun 2026.
Give AI agents a persistent pixel-art character reflecting their state in real time.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, args, { stdio: 'ignore' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cubelife -e 'CUBELIFE_API_KEY=<CUBELIFE_API_KEY>' -e 'CUBELIFE_AGENT_ID=<CUBELIFE_AGENT_ID>' -- npx -y cubelife
{
"mcpServers": {
"cubelife": {
"command": "npx",
"args": [
"-y",
"cubelife"
],
"env": {
"CUBELIFE_AGENT_ID": "<CUBELIFE_AGENT_ID>",
"CUBELIFE_API_KEY": "<CUBELIFE_API_KEY>"
}
}
}
}
[mcp_servers.cubelife]
command = "npx"
args = ["-y", "cubelife"]
env = { CUBELIFE_API_KEY = "<CUBELIFE_API_KEY>", CUBELIFE_AGENT_ID = "<CUBELIFE_AGENT_ID>" }
{
"mcpServers": {
"cubelife": {
"command": "npx",
"args": [
"-y",
"cubelife"
],
"env": {
"CUBELIFE_AGENT_ID": "<CUBELIFE_AGENT_ID>",
"CUBELIFE_API_KEY": "<CUBELIFE_API_KEY>"
}
}
}
}
{
"servers": {
"cubelife": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cubelife"
],
"env": {
"CUBELIFE_AGENT_ID": "<CUBELIFE_AGENT_ID>",
"CUBELIFE_API_KEY": "<CUBELIFE_API_KEY>"
}
}
}
}
Put your own values in place of
<CUBELIFE_API_KEY> (Agent API key from the CubeLife dashboard), <CUBELIFE_AGENT_ID> (Agent ID from the CubeLife dashboard).
The author’s registry entry marks them as required.
Persistent tmux terminal for AI agents — real-time spectating, SSH host-group dispatch.
MCP Server for Pixel Squads — observe your AI agents as pixel-art characters in a live office
Build personal interactive apps with real URLs and persistent storage, using any AI.
Agent intercommunication - messaging, channels, shared state, and real-time events
Persistent memory for AI coding agents. Install the memry CLI and run memry setup.
Persistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.
Stealth browser automation for AI agents — real Chrome, N parallel persistent logged-in sessions.
Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo.
Answers built from our own checks of this server.