> ## Documentation Index
> Fetch the complete documentation index at: https://docs.motion.so/llms.txt
> Use this file to discover all available pages before exploring further.

# ChatGPT App

Connect ChatGPT to Motion using a custom MCP app. Developer mode availability depends on your ChatGPT plan and workspace settings. Use these connection details:

| Field | Value |
| - | - |
| App name | `Motion` |
| Description | `Create and edit videos with Motion. Use this app for launch videos, explainers, promos, ads, trailers, motion graphics, product demos, social clips, article-to-video, and turning docs, sites, products, or ideas into videos.` |
| MCP URL | `https://mcp.motion.so/mcp` |
| Authentication | OAuth 2.1 with PKCE via Dynamic Client Registration or Client ID Metadata Documents |

Motion uses Streamable HTTP MCP. In supported ChatGPT clients, video tools display a live video card. Billing tools open checkout or Motion billing for you to review and complete.

## Connect in ChatGPT Developer Mode

1. Open **Settings -> Apps -> Advanced settings** and enable **Developer mode**.
2. Return to **Settings -> Apps** and choose **Create app**.
3. Enter the app name, description, and MCP URL above.
4. Choose OAuth. ChatGPT can use CIMD when the authorization server advertises
   `client_id_metadata_document_supported: true`, or DCR through
   `https://mcp.motion.so/oauth/register`.
5. Authorize your Motion account in the browser and approve the requested scopes.
6. In a conversation, choose **Developer mode** from the composer and enable
   **Motion**.

## Widgets

| Tool | Widget | Behavior |
| - | - | - |
| `list_engines` | None | Read supported engines and efforts |
| `list_templates` | None | Read account-accessible templates for an engine |
| `create_video` | `ui://motion/generation.html` | Starts a video job and shows a live card that updates as the video renders. |
| `create_followup` | `ui://motion/generation.html` | Revises an existing completed job or replies to pending user input and reuses the live video card. |
| `get_session_status` | `ui://motion/generation.html` | Reopens a job in the video widget and exposes `output.download_url` when complete. |
| `show_plans_and_credits` | `ui://motion/plans.html` | Shows plan cards, balance, hosted credit checkout, and billing links. The user completes payment and recurring billing changes in the browser. |

Use the video card to play or download the finished result. If the card is unavailable, ask your agent to check `get_session_status` and share the download link.

See the OpenAI Apps SDK docs for the current ChatGPT setup and review flow:

* [https://developers.openai.com/apps-sdk/build/mcp-server](https://developers.openai.com/apps-sdk/build/mcp-server)
* [https://developers.openai.com/apps-sdk/deploy/connect-chatgpt](https://developers.openai.com/apps-sdk/deploy/connect-chatgpt)
* [https://developers.openai.com/api/docs/guides/developer-mode](https://developers.openai.com/api/docs/guides/developer-mode)

## Engines available to your account

New video jobs use the default returned by engine discovery for your account. Motion Legacy requires an eligible account. Ask for "Motion with high effort" to choose `engine: "motion", effort: "high"`.

GVA availability follows your account's engine access. When available, it appears in your connected account's engine catalog and tool schemas with `standard` and `extended` effort. Ask for "GVA Standard" to use `engine: "gva", effort: "standard"`, or "GVA Extended" to use `engine: "gva", effort: "extended"`. Connecting ChatGPT does not grant Motion Legacy eligibility. Optional `engine`, `effort`, and `template` fields use the [shared engine contract](https://docs.motion.so/guides/engines.md). Existing connections and tool names remain valid, and follow-ups keep their project engine. MCP clients use `engine: "motion"` and `effort` for Motion. The REST-only `mode` input is not in the connector schema.

For the dedicated OpenAI connector profile, use `https://mcp.motion.so/mcp/openai`. It exposes video tools and sponsored generation, without billing tools. Its OAuth tokens must target that resource; a token for `/mcp` cannot be reused. Read the connected profile's schema for supported tools and inputs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.