Pixel Squads

io.github.aitor-altPublished by GitHub account aitor-altv0.1.1Updated Oct 24, 2026

MCP Server for Pixel Squads — observe your AI agents as pixel-art characters in a live office

VerifiedSTDIODesktop onlyAI & ML

Overview

AI-generated overview

Connects an assistant to Pixel Squads, which shows AI agents as pixel-art characters in a live office view.

What you can do
Pixel Squads is an MCP server that links an assistant to the Pixel Squads service, where AI agents are represented as pixel-art characters in a live office scene. The registry description says it is for observing your AI agents in that visual form. No tool list is published, so the exact operations the assistant can call are not documented here.
When to use it
Consider it if you already use Pixel Squads and want an assistant to connect to that workspace. Because no tools are documented, it is hard to judge other uses from the available information.
Requirements
Runs as a local process over stdio, installed from the npm package pixelsquads-mcp-server, so Node.js is needed. It requires the secret environment variable PIXEL_SQUADS_TOKEN, described as a Pixel Squads tenant API token obtained from the provider's site. Desktop only; no web executable.
Before you install
The server requires the secret PIXEL_SQUADS_TOKEN, a tenant API token that grants access to your Pixel Squads account; keep it out of logs and shared configuration. The published description does not state what data is sent to the Pixel Squads service or whether any actions modify your account, so review that before installing.

Installation

In SourceWeft

  1. Open Pixel Squads in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.