Motion for Muse

The Motion connector lets Muse create and revise videos, check render status, and buy more Motion credits with the user's approval. Motion is a product operated by Mosaic AI Labs, Inc.

Connection and permissions

Muse connects to https://mcp.motion.so/mcp/muse through OAuth authorization code with PKCE. A new user can create a free Motion account during connection; an existing user signs in and approves access. Motion binds each access token to the Muse resource and the user who approved it. API keys, device authorization, and service-account credentials are not accepted on this endpoint.

The connector requests five scopes:

Tool	Scope	Effect
list_engines	motion:sessions:read	Read supported engines and efforts
list_templates	motion:sessions:read	Read account-accessible templates for an engine
create_video	motion:sessions:write	Starts an asynchronous video job. The first Muse-created video per user is free. This write is not safe to retry automatically.
create_followup	motion:sessions:write	Revises an existing video. The first follow-up on the sponsored Muse video is free. This write is not safe to retry automatically.
get_session_status	motion:sessions:read	Reads the state and result of one video job owned by the connected user.
get_credit_balance	motion:credits:read	Returns the balance and exact one-time top-up offer for the connected account.
purchase_credits	motion:credits:purchase	Creates an idempotent payment link for the user-approved amount. Muse can pay it through HTTP 402/MPP and Link; the response also includes the Motion billing page as a browser fallback.

The protocol also requires the mcp scope. The Muse connector does not expose subscriptions, automatic top-ups, payment-method management, account administration, API keys, service accounts, uploads, external attachment URLs, style-reference URLs, or embedded UI resources.

Credits

The first video created through Muse and the first follow-up on that video are sponsored once per Motion user. A reply to Motion while that video is awaiting_user_input counts as the sponsored follow-up. Reconnecting Muse or using another Muse OAuth client does not reset either entitlement. Later video generations and revisions use the connected account's Motion credits.

If the account runs out of credits, Motion pauses and preserves the current job. Muse reads the exact top-up offer with get_credit_balance, asks the user to approve the amount, and calls purchase_credits. When MPP is enabled, Motion returns a short-lived payment URL. Muse posts to that URL, receives an HTTP 402 challenge, gets the user's approval through Link, and retries with a Shared Payment Token. Motion verifies the payment, adds the purchased credits once, and returns a payment receipt. The connector also returns https://motion.so/billing as a browser fallback. After payment, Muse continues the same job with create_followup. Status and balance checks do not use either free entitlement.

Data use

Motion processes the prompt and generated video data needed to complete the requested workflow. The Muse endpoint does not accept attachments and does not send proactive webhook events to Muse. Each status request is limited to a job owned by the connected Motion user.

See the Mosaic privacy policy and terms of service for the policies that govern Motion. Questions and data requests can be sent to [email protected] or submitted through Motion support.

Disconnect

To disconnect completely, Muse must revoke the access token and refresh token separately at https://mcp.motion.so/oauth/revoke, then remove its local copies. A later reconnect starts a new OAuth authorization.

Engine selection

New jobs default to GVA 1.0 with standard effort when the account has access, or Motion with medium effort otherwise. Optional engine, effort, and template fields use the shared engine contract. Existing tool calls remain valid, and follow-ups keep their project engine.

Engine access

Engine access follows your account permissions. Admins can use every engine; GVA requires GVA access, and legacy Motion is available to all signed-in users. Engine discovery lists only engines your account can use and marks your default. Template discovery without an engine uses that same default. When engine is omitted on a new job, GVA is the default for accounts with GVA access; other accounts use Motion. Explicit GVA requests without access return engine_access_required (HTTP 403) and never switch engines. Select engine: "motion" to use Motion. Access is checked again for every follow-up, including credit-pause resumes. API keys, OAuth scopes, templates, subscriptions, and sponsored turns do not grant engine access. Existing outputs remain readable by their owner.