Docs / MCP
Connect an MCP client
6 minute read · Updated 2026-09-11
Mint a token in Settings, point your client at https://app.artifexstudio.app/api/mcp with an Authorization header, and the whole tool surface appears. Setup takes about two minutes per client.
Before you start
- 01
Be on a Pro or Studio plan
MCP and API access is a paid capability. Free, Indie, and beta workspaces can sign in to the app but cannot mint a token.
- 02
Mint your token
In the app, go to Settings → MCP access → Generate token. The token starts with artk_ and is shown exactly once — copy it before you leave the page.
- 03
Store it somewhere your client can read
Treat it like a password. An environment variable or your OS keychain, not a file you commit.
Claude Code
One command. Run it in any project, or add --scope user to make it available everywhere.
claude mcp add --transport http artifex-studio https://app.artifexstudio.app/api/mcp \
--header "Authorization: Bearer artk_your_token_here"Verify it connected, then ask Claude to run a health check:
claude mcp listClaude Desktop
The simplest route is Settings → Connectors → Add custom connector, pasting the server URL. If your build does not offer custom connectors, or you want the token kept in the config file, bridge the remote server with mcp-remote.
{
"mcpServers": {
"artifex-studio": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://app.artifexstudio.app/api/mcp",
"--header",
"Authorization: Bearer artk_your_token_here"
]
}
}
}The config file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Restart Claude Desktop after editing it.
Cursor
Cursor speaks Streamable HTTP directly, so it takes the URL and headers as-is.
{
"mcpServers": {
"artifex-studio": {
"url": "https://app.artifexstudio.app/api/mcp",
"headers": {
"Authorization": "Bearer artk_your_token_here"
}
}
}
}Any other client
Anything that supports remote MCP over Streamable HTTP will work. Give it the URL and one header; there is nothing else to configure.
Connection parameters
urlstringrequired- https://app.artifexstudio.app/api/mcp
transportstringrequired- http (Streamable HTTP). Not stdio, not SSE.
Authorizationheaderrequired- Bearer artk_… — your workspace token.
toolsetsquery param- Optional. all (default), dynamic, or a comma-separated folder list.
Verify it works
Ask your agent to call health_check. It needs no arguments and touches no data, so it isolates the connection from everything else. Then try a read that proves the token resolved to the right workspace:
"Check that Artifex Studio is connected, then list my artists
and the songs for the first one."If the tools are present but every read comes back empty, the token is valid but pointing at a workspace with no data — check which account you minted it from.
Keep going