Documentation for LLMs

LLMs are trained on web data that's often years old, which means they're often not up-to-date on latest APIs.

With Motion for AI, it's possible to provide the latest documentation to your LLM to help it understand the latest version of Motion.

There are two ways Motion for AI lets your load docs into your LLM:

• MCP Resources (preferred, but not currently supported by Cursor)

• lllms.motion.dev

MCP Resources

The latest Motion documentation is exposed as Resources via the Motion MCP server.

The benefit of using Resources over llms.motion.dev is that they're faster to access and browsable.

Additionally, Motion+ users can use the Motion+ MCP server to access docs for Motion+ exclusive and early access APIs.

Install

Documentation is provided via Motion for AI's MCP server. Add the following to your editor's MCP JSON settings:

{
  "mcpServers": {
    "motion": {
      "command": "npx",
      "args": ["motion-ai"]
    }
  }
}

The exact process differs by editor, but here are the MCP docs for popular apps:

• VS Code

• Cursor (Note: Does not currently support resources)

• Windsurf

• Claude Desktop

• Claude Code

Usage

Windsurf

In Windsurf, a Resource can be referenced directly in your prompt using @resources. This will open a selection menu where you can choose the documentation you want to attach.

Claude Desktop

In Claude Desktop, a Resource currently has to be manually attached to the current prop via the + button.

From here, you can select Add from motion, which will display a full list of docs.

The "Search menu" at the top can help you narrow down this list to only the APIs you're looking for.

llms.motion.dev

llms.motion.dev offers Motion documentation in Markdown format, which makes it lighter than attaching a full documentation page.

Usage

Every page in the Motion documentation has an LLM-friendly equivalent. For instance, motion.dev/docs/inview becomes llms.motion.dev/docs/inview.md.

All editors will accept a direct link to a documentation page.

Windsurf

Windsurf specifically can take just "llms.motion.dev" and is smart enough to navigate to the page relevant to the current topic:

Explain how to use useInView llms.motion.dev

Cursor

Cursor must be given a direct URL to the relevant documentation. It's also possible to add documentation via Cursor Settings > Indexing and Docs > Docs but it isn't currently smart enough to follow the Markdown links on llms.motion.dev. Instead, the main docs website motion.dev/docs must be provided:

This is more wasteful in terms of tokens but the whole docs will be correctly indexed.