Pixel Engine MCP

A remote MCP server provided by Pixel Engine that allows AI agents to generate, animate, and clean up pixel art assets. It supports tools for generating sprites, animating still images, pixelating images, and removing backgrounds, utilizing OAuth 2.1 authentication and a credit-based billing system.

Visit Pixel Engine

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Vendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Pixel Engine

You need:Sign in / Create accountOAuth 2.1 with dynamic client registrationPixel Engine API key is also accepted as the bearer token

MCP endpoint (Streamable HTTP)

https://api.pixelengine.ai/functions/v1/mcp

Vendor documentation

What you can do with it

Generate pixel-art sprites from text prompts
Animate static pixel art images
Convert standard images to pixel art style
Remove backgrounds from images

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: ai.pixelengine/mcp@1.0.0 Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 185 ms
95th percentile latency: 185 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 6:58 AM UTC · probe · passed · 185 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http pixel-engine-mcp https://api.pixelengine.ai/functions/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add pixel-engine-mcp --url https://api.pixelengine.ai/functions/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pixel-engine-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "pixel-engine-mcp": {
      "url": "https://api.pixelengine.ai/functions/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "pixel-engine-mcp": {
      "type": "streamableHttp",
      "url": "https://api.pixelengine.ai/functions/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pixel-engine-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "pixel-engine-mcp": {
      "type": "http",
      "url": "https://api.pixelengine.ai/functions/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http pixel-engine-mcp https://api.pixelengine.ai/functions/v1/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "pixel-engine-mcp": {
      "url": "https://api.pixelengine.ai/functions/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "pixel-engine-mcp": {
      "serverUrl": "https://api.pixelengine.ai/functions/v1/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Pixel Engine MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 3,755

Do you run Pixel Engine MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing