Client configuration

Before configuring a client

Create an API key in your own account with the scopes needed for the intended workflow. Set SPRITEFLOW_API_KEY in the environment that starts the client; a variable set in an unrelated terminal may not be visible to a desktop app. Restart or reload the client after changing its configuration.

The templates below use the hosted endpoint. When testing locally, replace the URL with the same local deployment used to create the key. Do not paste a real secret into a shared configuration file.

Codex

Save this in ~/.codex/config.toml.

1[mcp_servers.spriteflow]
2url = "https://spriteflow.io/api/mcp"
3bearer_token_env_var = "SPRITEFLOW_API_KEY"

Official client documentation

Claude Code

Save this in .mcp.json.

1{
2  "mcpServers": {
3    "spriteflow": {
4      "type": "http",
5      "url": "https://spriteflow.io/api/mcp",
6      "headers": {
7        "Authorization": "Bearer ${SPRITEFLOW_API_KEY}"
8      }
9    }
10  }
11}

Official client documentation

Cursor

Save this in .cursor/mcp.json.

1{
2  "mcpServers": {
3    "spriteflow": {
4      "url": "https://spriteflow.io/api/mcp",
5      "headers": {
6        "Authorization": "Bearer ${env:SPRITEFLOW_API_KEY}"
7      }
8    }
9  }
10}

Official client documentation

Check the connection

Use the client's MCP tool discovery and the API & MCP settings connection check. Authentication and tools/list spend no credits. A 401 means the key is invalid, expired or no longer allowed to authenticate; 403 means access or scope is insufficient. A service-configuration error must be fixed before key creation or callback use.

Then run the MCP quickstart. Client configuration syntax and successful discovery are separate from a verified end-to-end paid generation. No OAuth, SSE subscription or experimental MCP Tasks support is required.