Axiom Lab

npx add-mcp 'https://axiomlab.online/mcp'

Connect Axiom Lab over MCP so an AI assistant such as Claude or Cursor can upload, plan, produce and download for you.

Connect

The remote MCP server is https://axiomlab.online/mcp. There is nothing to install; authenticate with the header Authorization: Bearer <API key>.

Create a key at https://axiomlab.online/dev under Developers → Overview → API keys.

The remote server cannot read files on your computer: the assistant sends file contents instead, up to 20 MB per file.

Claude Code

claude mcp add --transport http azimo https://axiomlab.online/mcp --header "Authorization: Bearer $AZIMO_API_KEY"

Cursor

Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "azimo": {
      "url": "https://axiomlab.online/mcp",
      "headers": {"Authorization": "Bearer ${env:AZIMO_API_KEY}"}
    }
  }
}

Then just ask: "Make a 30-second product video for the Pliva Fold Kettle from./kettle-spec.pdf."

What the assistant can and cannot do

It can list workflows and the fields each type needs, upload files you point it to, create plans, start production once you agree, follow progress, and hand you the download links. Once your material has been read it tells you the suggested length and continues with the seconds you confirm; it can approve an approvable budget stop after you say yes. It can also show your balance and cancel videos.

It must show you the plan first. Production can only start from a plan, and the tools tell the assistant to show you the plan (workflow, length, format) and wait for your explicit yes. Starting production, approving extra spending and cancelling are marked as actions that need confirmation, so most clients ask you before running them. Repeating the start call on the same plan returns the same video.

It cannot see or quote prices (contact sales@axiomlab.online for pricing), get around your balance and limits, or read your computer's files.

Stay safe

• Give each client its own key, so a leak means revoking just that one.
• If the assistant only needs to check progress, give it a viewer key: it cannot create plans or start production.
• Never paste a key into a chat; keep it in an environment variable or the config file.

Troubleshooting

• HTTP 401: the key is missing, wrong or revoked. Check the header in your client's configuration.
• 403 read-only key: you are using a viewer key; switch to editor or owner.
• 402: not enough balance, or a spending limit was reached.
• The plan is needs_input: fix what requirements lists; for example materials_required means there is no file, unsupported_duration means the length is outside the workflow's range and unsupported_aspect_ratio means the format is not supported.
• A video waits at needs_input with code confirm_duration: tell the assistant how many seconds you want; it confirms the length and production continues.

See Advanced usage, Skills and the API reference for more.