Creaa MCP · Streamable HTTP

Give AI agents direct access to image and video generation

Connect Creaa's live model catalog, cost estimation, image editing, and video generation to your agent. Discovery, billing, and durable job state share the same reliable Open API backend.

MCP URL https://creaa.ai/mcp/server
agent ↔ creaa
›Find a 9:16 model for a product ad
tool · list_models
{ "type": "video", "aspect_ratio": "9:16" }
tool · estimate_cost
{ "model": "seedance-2.5", "duration": 5, "resolution": "480P" }
→ 115 credits · exact estimate
✓Waiting for confirmation before generation
CodexAvailable now
Claude CodeAvailable now
CursorAvailable now
OpenClawHTTP / Skill
HermesAvailable now
ChatGPTOAuth available
Get started

Connect Creaa to your agent in three steps

No new server or domain required. The website, Open API, and MCP continue to run on the existing Creaa infrastructure.

1

Prepare your connection

Create a connection key in Profile. New/re-authorized OAuth generation spends website credits, without Unlimited. Old connections without website-credit consent keep API credits. Direct ck_ keys retain their independent API balance; balances are not merged. Open Profile →

2

Enable MCP access

Click Enable MCP on that key. Access is off by default, controlled per key, and can be revoked anytime.

3

Add the remote endpoint

Add the MCP URL and Bearer key to a Streamable HTTP client, then ask the agent to list its tools.

Connection

Choose an MCP client or CLI

Agents can connect over MCP, while terminals and automation can install the dependency-free Creaa CLI. The CLI supports browser OAuth and remains compatible with existing API keys.

1

Copy the Creaa MCP URL

Create and enable an MCP key, then copy the remote endpoint.

https://creaa.ai/mcp/server
2

Add it to config.toml

Keep the key in an environment variable, never in config or source control.

export CREAA_API_KEY="ck_your_key"

[mcp_servers.creaa]
url = "https://creaa.ai/mcp/server"
bearer_token_env_var = "CREAA_API_KEY"
3

Start and check the tools

Start Codex and ask it to list the Creaa tools; it should find 10.

codex
› List the available Creaa tools

10 MCP tools

OAuth available

Claude

Add the Creaa MCP URL as a custom connector in Claude. New/re-authorized OAuth on the updated consent page permits generation to spend website credits without Unlimited. Old connections without that consent keep API credits; reconnect and re-authorize to switch. No raw key is pasted into the client.

1

Copy the remote endpoint

Enable MCP access for the selected key in Profile first.

https://creaa.ai/mcp/server
2

Add mcp.json

Add Creaa to the project or global configuration.

{
  "mcpServers": {
    "creaa": {
      "url": "https://creaa.ai/mcp/server",
      "headers": {
        "Authorization": "Bearer ${env:CREAA_API_KEY}"
      }
    }
  }
}
3

Reload and start creating

Reload Cursor's MCP configuration, then ask the agent to call list_models.

› Use Creaa list_models
› Generate only after I confirm

Charge after confirmation

1

Prepare the MCP key

Enable MCP access and put the key in the current terminal environment.

export CREAA_API_KEY="ck_your_key"
2

Run the Claude Code command

Use the remote HTTP transport and Authorization header.

claude mcp add --transport http creaa https://creaa.ai/mcp/server \
  --header "Authorization: Bearer ${CREAA_API_KEY}"
3

Check the connection

Start Claude Code and ask it to read Creaa's live models.

claude
› List Creaa image models

Streamable HTTP

1

Create an MCP key

Enable MCP and copy the endpoint; the configuration stays in your local OpenClaw user config.

https://creaa.ai/mcp/server
2

Add the remote MCP

Replace ck_your_key with an MCP-enabled test or production key.

openclaw mcp set creaa \
'{"url":"https://creaa.ai/mcp/server","transport":"streamable-http","headers":{"Authorization":"Bearer ck_your_key"}}'
3

Check and use it

Confirm the configuration, then call Creaa tools in an OpenClaw conversation.

openclaw mcp show creaa
openclaw mcp list

OpenClaw guide

1

Copy the Creaa endpoint

Enable an MCP key in Profile; Hermes stores the token in the active profile's .env.

https://creaa.ai/mcp/server
2

Let Hermes discover the tools

The command securely prompts for the Bearer key and should discover 10 tools.

hermes mcp add creaa \
  --url https://creaa.ai/mcp/server \
  --auth header
3

Test and start

Test the connection, then start Hermes and ask it to use Creaa.

hermes mcp test creaa
hermes
› Use Creaa to list image models

Hermes MCP

OAuth available

ChatGPT

Add the Creaa MCP URL as an OAuth custom connection. New/re-authorized OAuth on the updated consent page permits generation to spend website credits without Unlimited. Old connections without that consent keep API credits; automatic refresh does not switch wallets. Reconnect and re-authorize to switch. Access can be revoked at any time.

1

Choose the transport

The client must support Streamable HTTP and custom headers.

Transport: Streamable HTTP
2

Enter connection details

Never commit or share the key.

URL: https://creaa.ai/mcp/server
Authorization: Bearer ck_your_key
3

Initialize the connection

Start with tools/list and list_models; neither incurs a charge.

initialize
tools/list
tools/call → list_models
1

Install Creaa CLI

Works on macOS and Linux with only Python 3. The installer verifies the CLI before writing it to ~/.local/bin.

curl -fsSL https://creaa.ai/cli/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
creaa --version

2

Sign in securely

Browser OAuth uses PKCE and stores rotating tokens with 0600 permissions without exposing the raw key. New/re-authorized OAuth generation spends website credits without Unlimited. Old connections without website-credit consent keep API credits; reconnect and approve the updated page to switch, not just refresh tokens. creaa login --api-key retains the independent API balance.

creaa login
creaa account status

OAuth + PKCE with automatic refresh

3

Discover and generate

Read the live catalog and estimate first, then submit once with a stable idempotency key.

creaa model list --type image

creaa generate image \
  --prompt "A cinematic product photo" \
  --model "paste-model-id-here" \
  --idempotency-key "my-first-image" \
  --wait

creaa 0.3.0

10 MCP tools

A complete loop from discovery to results

The tool surface stays small and stable. Agents do not guess endpoints or spend credits before confirmation.

account_status

Balance, plan, and rate limits

list_models

Read the live image and video catalog

get_model

Inspect one model's parameters and limits

estimate_cost

Estimate exact credits before submit

generate_image

Generate images with count and ratio

edit_image

Edit and restyle reference images

generate_video

Text, image, and reference-to-video

get_job

Read the latest durable job state

wait_job

Wait safely until completion or timeout

list_jobs

Recover job history across sessions

Safety by design

Let agents act without silent spending

Estimate first

Return exact credits and affordability before generation.

Explicit confirmation

Generation submits only when confirm=true is present.

Duplicate protection

Idempotency keys prevent duplicate jobs during retries.

Per-key access

MCP is off by default; enable, disable, and revoke take effect immediately.

19 live models

One agent, leading models across providers

Models and pricing come from the live catalog instead of being hardcoded into the client.

video

Seedance 2.5

seedance-2.5
video

MiniMax H3

minimax-h3
video

Seedance 2.0

seedance-2.0
video

Seedance 2.0 Fast

seedance-2.0-fast
video

Veo 3.1

veo-3.1
image

Seedream 5.0

seedream-5.0
image

Seedream 5.5

seedream-5.5
image

Nano Banana 2

nano-banana-2
FAQ

Questions before connecting

Does this affect the existing Open API?

No. MCP is a compatibility layer over /api/open/v1; existing paths, keys, billing, and job APIs remain unchanged.

Do I need another server or domain?

No. Both the page and protocol endpoint live on creaa.ai; the MCP process listens only on loopback behind Nginx.

Why are the page and protocol different URLs?

/mcp is for people; /mcp/server receives protocol requests. Separate paths make browser, cache, and authentication behavior explicit.

Which credit balance does MCP use?

New/re-authorized OAuth generation spends website credits, without Unlimited. Legacy OAuth without website-credit consent keeps API credits; reconnect and approve the updated consent page to switch. Automatic refresh does not switch wallets. Direct legacy ck_ API keys retain an independent API wallet unchanged. Existing API balances are not merged or transferred. Credit grants and expiry rules are unchanged.

Put Creaa in your agent's hands

Create an API key, enable MCP access, and connect one remote endpoint. Existing API users and integrations remain unaffected.

Connect now