Connect Codex to SceneSmith

01

Use the hosted endpoint

SceneSmith provides a remote MCP server over HTTPS. Your client sends requests to the endpoint below, while SceneSmith keeps workspace data, provider credentials, and workers server-side.

https://app.scenesmith.design/api/mcp

02

Recommended: connect with OAuth

Use OAuth when the client supports remote MCP authorization. The client opens SceneSmith in a browser, you sign in, choose the workspace, and approve only the requested scopes.

• Add a remote MCP server in the client.
• Use the hosted endpoint above.
• Complete the browser authorization and return to the client.
• Start with the read-only smoke test below.

03

Fallback: use a workspace API key

If the client cannot complete OAuth, an owner or admin can create a separately revocable connection in the SceneSmith app. The full key is shown once and is hashed at rest.

• Open Accounts and choose Connect an IDE.
• Create a connection with only the scopes the client needs.
• Copy the key immediately and store it in the client's private secret store.
• Send it as an Authorization bearer token. Never commit it or paste it into a prompt.

04

Common client configuration

For clients that accept a remote URL and private headers, use this shape. The exact environment-variable syntax varies by client.

{
  "url": "https://app.scenesmith.design/api/mcp",
  "headers": {
    "Authorization": "Bearer ${SCENESMITH_MCP_TOKEN}"
  }
}

05

Run this first

After connecting, ask the client to inspect the workspace without starting work or changing the calendar.

Connect to SceneSmith production. Do not run research, generate a video, modify the calendar, or publish anything. Call list_projects, get_project_context, get_daily_brief, and list_runs. Report the authorized workspace, policy, and whether the connection is read-only.

06

What the connection can do

The hosted gateway lets an approved client read context, start durable research or video work, monitor runs, create calendar drafts, and revise copy. Publishing stays behind workspace policy and explicit approval.

• Read projects, context, runs, calendar state, and daily briefs.
• Start research and receive a durable run ID.
• Start or revise video work and inspect signed previews.
• Draft calendar content without publishing it.
• Approve delivery only when the workspace policy and owner permission allow it.