Neonix MCP — Motion infrastructure for AI agents

A standard bridge between an AI client and Neonix.

What is MCP?

Model Context Protocol lets a compatible AI client discover structured tools and call them with validated inputs. Instead of asking an agent to print a large HTML file in chat, Neonix lets it work with a real project through a controlled remote connection.

Neonix remains responsible for authentication, workspace ownership, revisions, HTML validation, preview, and export. The agent supplies intent; Neonix keeps the project safe.

Streamable HTTP / OAuth / Raw HTML / Preview and export

Get started

No local renderer or package is required. Connect to the URL, sign in with your Neonix account when OAuth opens, and approve access to the workspace you want the client to use.

Hosted MCP endpoint:

https://api.neonix.video/mcp

Use a remote MCP client — Choose a host that supports Streamable HTTP MCP connections.
Authorize Neonix — OAuth connects the client to your account and workspace permissions.
Start with an HTML project — Ask the agent to create a complete HTML/CSS project.

Supported clients

Neonix's hosted MCP connection works the same way for every client: add the endpoint, complete OAuth, done. No API key or client ID to copy in — supported clients complete OAuth automatically when you add the connector, and any other MCP client registers itself the same way over standard OAuth dynamic client registration.

Chat apps — connect through the app's own settings UI:

Client	Description
Claude	Create and refine motion projects from a conversation.
ChatGPT	Turn structured intent into editable motion and exports.
Grok	Give Grok a secure connection to your Neonix workspace.

Developer tools — connect with a CLI command or a config file:

Client	Description
Claude Code	Add Neonix as a remote MCP server from the terminal.
Codex	Add Neonix to Codex's `config.toml` and call it from a session.
Cursor	Add Neonix to `mcp.json` and call it from the editor's agent.
Antigravity	Add Neonix to Antigravity's shared MCP config for its CLI and IDE.

Continue with Claude, ChatGPT, Grok, Claude Code, Codex, Cursor, or Antigravity.

Tools

The remote server exposes focused tools instead of one opaque generate call. Each operation is authenticated, validated, and scoped to the user's workspace.

Group	Description	Tools
Workspace & projects	Find workspaces and projects, rename them, open a preview, or delete them.	`list_workspaces`, `list_projects`, `get_project`, `update_project`, `open_preview`, `delete_project`
HTML authoring	Store complete HTML/CSS as-is as the project source; it is rendered frame by frame.	`create_project_html`, `get_project_html`, `update_project_html`
Assets	List, upload, import, attach, and safely remove workspace media assets.	`list_assets`, `request_asset_upload`, `complete_asset_upload`, `import_asset`, `attach_asset_to_project`, `delete_asset`
Export jobs	Create an export from the project HTML, follow its status, and retrieve the result.	`create_export`, `get_export`, `get_export_download_url`, `cancel_export`

Recommended workflow

Start high-level, keep the source and revision history clear.

Create — Prepare a complete neonix-document (or omit html to start from the blank template), then use create_project_html.
Edit — Read with get_project_html, preserve the document metadata, then save with update_project_html.
Ship — Show the result with open_preview, create an export, and retrieve the signed download URL when ready.

create_project_html -> open_preview
get_project_html -> update_project_html
create_export -> get_export -> get_export_download_url

Resources and prompts

neonix://docs/workflows — recommended create, edit, asset, and export flows.
neonix://docs/html-authoring — the HTML document contract and the rules checked when saving.

Compatible hosts can attach the create_html_project and edit_html_project prompts and the resources above to give the agent the Neonix workflow before it calls a tool.

Important boundaries

HTML is the project source; it is stored as-is and rendered frame by frame, with no compile step.
Exports run from the saved project HTML, not from unsaved content supplied in a tool call.
Destructive actions such as delete_project, delete_asset, and cancel_export should be confirmed first.