AI assistants

An AI assistant can build and change your AR Clip projects for you. There are four ways to use one — pick the one that fits the tools you already have.

Pick a way

Way	What the assistant can do	What you need
Built-in assistant	build and change your scene directly	nothing — it is in the editor
Your AI app, over MCP	the same, from Claude, Cursor or any other app that supports MCP	to sign in once in the browser
A coding agent in a folder	build, check and preview a project from the terminal	the arclip CLI
Any chat model (GPT, DeepSeek, Perplexity and others)	give advice, and write scripts and patch graphs for you to paste	the brief

Built-in assistant

This is the quickest way to start. Click the top icon in the editor's left rail and describe what you want. The assistant builds it.

Everything it makes is ordinary project content, so you can change it by hand afterwards. See AI assistant panel.

Your AI app, over MCP

MCP (Model Context Protocol) is a standard way for AI apps to use outside tools. If you already use an app that supports it — Claude Desktop, Claude Code, Cursor and others — you can connect it to your project. It builds while you watch in the editor.

See Connect via MCP.

A coding agent in a folder

If you use a coding agent in a terminal, run arclip link in a folder. In one step it sets the folder up for Claude Code:

• the MCP server, tied to your project;
• the routine the agent should follow;
• commands to check the project, render a picture, run tests and open the draft on your phone.

Codex, Cursor and other agents can use the same MCP server and commands. arclip link writes an AGENTS.md for them, and arclip skill install --mcp adds the server and a guide to their settings.

See Command line.

Any other chat model

A model without MCP cannot change your project. It can still help: write a script, design a patch graph, or work out why something does not fire.

It needs context first, because no model knows AR Clip. Give it one page: Brief for assistants.

Paste the brief, then ask your question

The brief is written to be handed to a model as it is. It explains how projects are built, how things are named, and the mistakes that lead to wrong answers most often.

What to expect

Assistants are good at the tedious work: making forty objects, adding the same event to a list of objects, writing a script you would rather not write, working out what a step does.

They are weaker at judgement: how your experience should feel, whether a marker will track in the room where it will hang, how big something must be to read from three metres away.

Let assistants find the docs

Many AI tools look for a file called /llms.txt on a website. Ours lists the brief first. /llms-full.txt has every page in one file.

So "read the AR Clip docs" is often enough — you do not have to paste anything. You can also get any page as plain Markdown by adding .md to its address. Docs for AI assistants lists every option.

Never paste a key into a chat

No one legitimate will ask for it — not us, not a plugin, not an assistant. Tokens belong in your account settings.

Pages in this section

Connect via MCP

Connect Claude, Cursor or another AI app to your project.

Command line

Let a coding agent build, check and test your project from a folder.

Use cases

Jobs an assistant does well in AR Clip.

Skills

The guides the built-in assistant reads, and how to ask for one.

Brief for assistants

One page to give any chat model before you ask it for help.

AI assistant panel

The assistant built into the editor.

---

Next: Connect via MCP — connect your AI app to a project.