Artifex Studio / Docs
Build
on Studio
Everything the app can do is available to an MCP client. Connect Claude, Cursor, or your own code to your workspace and run the studio from a conversation.
- Tools exposed over MCP
- 98
- Toolset folders
- 9
- Streamable transport, stateless
- HTTP
01
Get started
What Studio is, the objects it works with, and how to reach it programmatically.
4 min readOverviewTechnical documentation for Artifex Studio — the objects it works with, and how to drive the whole workspace programmatically over MCP.5 min readCore conceptsThe objects Artifex Studio works with — workspaces, artists, songs, media assets, artstyles, jobs — and the rules that connect them.
02
MCP
Connect an MCP client to your workspace and drive the full tool surface.
5 min readMCP overviewA remote Model Context Protocol server that exposes the entire Artifex Studio tool surface to Claude, Cursor, or any MCP client.6 min readConnect a clientCopy-paste configuration for Claude Code, Claude Desktop, Cursor, and any other MCP client that speaks Streamable HTTP.4 min readAuthenticationHow Artifex Studio API tokens work — minting, scope, rotation, revocation, and what a token can reach.4 min readToolsetsThe nine tool folders, how to load only the ones you need, and how dynamic mode keeps small context windows usable.5 min readAgent SkillA downloadable Agent Skill that teaches any skills-compatible AI agent how to drive the Artifex Studio MCP server properly — workflows, polling discipline, and the traps.
03
Reference
Every tool, every folder, generated from the running server.
04
Operate
Jobs, credits, limits, and what to do when something fails.
6 min readJobsHow Artifex Studio runs renders asynchronously — launching, polling, reading progress, cancelling, and what a failure looks like.4 min readCredits and limitsWhat consumes credits in Artifex Studio, how reservations and refunds work, and the limits that apply to API callers.5 min readTroubleshootingThe errors you will actually hit when driving Artifex Studio over MCP, what each one means, and how to resolve it.
Not what you were after
The craft side of the work lives in the field notes.
These pages cover the API. For what actually makes a release travel — cut rhythm, format choices, how much content one track is really worth — read the field notes instead.
Read the field notes →