Automation · MCP

Connect your AI assistant

The Artimic MCP server is a remote, protocol-standard endpoint. The connection details are the same for every client — only the config syntax differs. Pick yours below.

Endpoint
Transport: Streamable HTTP (JSON-RPC)
Auth: Bearer · Free · 1000 calls/mo

Step 1 — paste your token

Tokens auto-fill the snippets below

Get a free token at Dashboard → API tokens. Default scope mcp:invoke is what you want. Stored only in your browser localStorage — never sent to us.

Get your free token →

No token set — snippets show art_live_YOUR_TOKEN; replace before pasting into your AI client.

Claude Code

One CLI command. The simplest path.

BASH

claude mcp add artimic \
  --transport http https://artimic.com/api/mcp \
  --header "Authorization: Bearer art_live_YOUR_TOKEN"

# Project scope (commits to .mcp.json — don't commit the literal token; use ${ARTIMIC_TOKEN})
claude mcp add artimic --scope project \
  --transport http https://artimic.com/api/mcp \
  --header "Authorization: Bearer ${ARTIMIC_TOKEN}"

Verify

claude mcp list
# artimic   http   https://artimic.com/api/mcp

First conversation after connecting

Try this prompt verbatim in your assistant:

Use the Artimic MCP server. Call get_editor_capabilities, then call render_design with a small Instagram-post intent — black background, white text saying "Hello", and a blue rectangle below the text. Save the returned bytes to ./hello.img.

Open the resulting .img in the editor — every layer stays editable.

Errors you might see

Status	Meaning	Fix
`401`	Missing or invalid token	Check the `Authorization` header. The token may be revoked.
`403`	Token missing `mcp:invoke` scope	Create a new token with the default scope.
`402`	Monthly call quota exhausted	Resets next month. Paid plans coming.
`5xx`	Server-side issue	See Troubleshooting.

What your assistant can do → Manage tokens Troubleshooting