Docs / MCP
The Artifex Studio MCP server
5 minute read · Updated 2026-09-11
Artifex Studio ships a hosted MCP server at /api/mcp. It speaks Streamable HTTP, authenticates with a per-workspace bearer token, and exposes the same tool registry the in-app agent uses — the library, every generation pipeline, strategy, and content tools.
What MCP is, briefly
The Model Context Protocol is an open standard for connecting AI assistants to external systems. A server publishes a set of typed tools; a client — Claude Code, Claude Desktop, Cursor, or something you wrote — discovers those tools and lets the model call them.
The practical consequence for Studio: instead of clicking through the app, you can say what you want in a conversation and let the agent do the lookups, launch the renders, and poll them to completion. The account, its tenancy, its credits, and its plan limits are identical either way. Nothing about the API bypasses the rules the UI follows.
Endpoint and transport
| Property | Value |
|---|---|
| URL | https://app.artifexstudio.app/api/mcp |
| Transport | Streamable HTTP (JSON responses) |
| Methods | POST, GET, DELETE |
| Auth | Authorization: Bearer artk_… |
| Sessions | None — the transport is stateless |
| Server name | artifex-studio |
| Required plan | Pro or Studio |
The server is stateless by design: every request builds a fresh server and transport, so nothing is retained between calls or across warm instances. There is no session id to manage and no connection to keep alive — each call carries its own authentication and stands alone.
What the server exposes
Around ninety-eight tools, grouped into nine folders. Remote clients get the complete surface by default — you do not need to opt into anything to reach the whole app.
| Folder | Covers |
|---|---|
| jobs | Poll and cancel background work. Always enabled, in every mode. |
| library | Artists, songs, media assets, saved waveform sections, pillars, campaigns, briefs. |
| generation | Image generation, cover art, photo studio, and every render pipeline. |
| media | Song and asset records, plus artstyle creation and refinement. |
| strategy | Brand guide, audience personas, per-platform strategy. |
| content | Content ideas, posts, and generated copy. |
| discography | Releases. |
| artist | Artist records and artist events. |
| settings | Health check and integration configuration. |
The full list — every tool name, whether it is sync or job, and what it does — is on the tool reference page, generated directly from the running registry.
Calling it without a client
MCP is JSON-RPC over HTTP, so you can drive it with curl or any HTTP library. Send the Accept header with both content types — the Streamable HTTP spec requires it, and omitting it is the most common reason a hand-rolled request is rejected.
curl -s https://app.artifexstudio.app/api/mcp \
-H "Authorization: Bearer $ARTIFEX_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }'curl -s https://app.artifexstudio.app/api/mcp \
-H "Authorization: Bearer $ARTIFEX_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "find_song",
"arguments": { "query": "midnight" }
}
}'Keep going