Build with the Moosky API and MCP

API overview

API base URL: https://api.moosky.ai.

Create an API key to receive a client_id and client_secret. Exchange them with a JSON POST to https://api.moosky.ai/auth/api-key/token. Send the returned token as Authorization: Bearer <token>. MCP-key tokens last one hour; API-key tokens remain valid until the key is revoked — exchange again whenever you get a 401.

GraphQL endpoint: https://api.moosky.ai/graphql. Use the explorer's Docs panel to browse queries, mutations, and types.

MCP quickstart

1. Create a key of type MCP with mcp:read, mcp:write, and mcp:generate. Select the servers your client needs.
2. Exchange the key for a bearer token using the API endpoint above. Send the returned token in your MCP client's Authorization header.
3. Connect with Streamable HTTP at https://api.moosky.ai/mcp/{slug}. Use tools/list to discover the tools currently available.
4. Use platform_create_project and platform_create_scene on the platform server before generation. Pass the resulting sceneId to the generation tool.

Servers: platform, video, image-edit, music-generate, text-to-image, text-to-speech, upscale-video, upscale-image, and utilities.

mcp:read permits reads, mcp:write permits project and scene changes, and mcp:generate permits generation that spends credits. mcp:project-video is reserved and cannot be selected. MCP currently exposes single-clip tools; the full Project Director workflow is not exposed.

Example server: https://api.moosky.ai/mcp/platform. MCP requests use POST; opening the server URL in a browser does not list its tools.

Models and pricing

API and MCP generation use the same credit billing as the portal. Model base costs, capabilities, current and retired status, credit packages, and subscription availability are published in Moosky platform facts (JSON). Options and usage can add to a model's base credit cost.