From the maker

SpriteFuse connects MCP clients to 11 tools for 2D game characters, animations, sprite revisions, owned jobs/projects/assets, private reference uploads, frame timing, and asset export. Connect via Streamable HTTP with OAuth. Generation uses account Credits and an explicit maximum credit budget per request. Trial credits are for personal, noncommercial evaluation. The public repository contains client connection configs and docs; the hosted backend is proprietary.

How to connect

Streamable HTTP endpoint:

https://spritefuse.com/api/mcp

What happened when we asked

We asked on 15 October 2026 and it challenged us for credentials. That is a working server guarding itself: it answered, and it wants an account we do not hold. A tool count and a response time come from a tools/list we were never served, so this listing carries neither.

How it asks you to sign in

Its refusal named a public document describing how to authenticate, which is what the MCP authorization spec asks a guarded server to publish. We read that document on 15 October 2026. Everything below is what it says; we have still not been inside this server.

Sign in through

spritefuse.com

Token accepted in

header

Read

2026-10-15 05:04 UTC

The 5 permissions it declares

These are the scopes the document lists, verbatim. They describe what an account can grant this server, not what it will do with the grant, and we have not audited either.

• account:read
• assets:read
• jobs:write
• jobs:cancel
• exports:write

Anything above describes one moment on the date shown. We do not re-test on a schedule, so nothing here says what this server is doing now. We have not audited its code, its data handling or its permissions, and this is not a safety rating.