Connect an AI assistant with MCP

Connect Scene Dept. to ChatGPT or Claude with OAuth, choose project access, understand permissions, and revoke a connection.

Scene Dept. can connect to a compatible AI assistant through the Model Context Protocol (MCP). The assistant uses Scene Dept.'s production tools while your projects remain protected by your live account permissions and the access you approve.

Scene Dept. supports OAuth connections only. You never copy a Scene Dept. password or a long-lived manual token into an assistant.

Before you connect

You need:

A verified Scene Dept. account.
A compatible assistant account or workspace that allows custom remote MCP connections.
The hosted Scene Dept. MCP URL: https://www.scenedept.com/mcp.

Hosted assistants cannot connect to localhost. The production endpoint must be used outside local protocol testing.

Connect from ChatGPT

Scene Dept. is not yet listed in the ChatGPT Plugins Directory. Until the public beta and review gates are complete, eligible accounts can test it as a custom MCP connection in developer mode.

In ChatGPT, open Settings, then enable Developer mode. Availability and the exact controls depend on your account and workspace policy.
Open ChatGPT Plugins, select the add button, and create a connection.
Enter https://www.scenedept.com/mcp as the public MCP server URL.
Create the connection and complete the Scene Dept. sign-in and consent flow.
Review the discovered tools before using the connection in a chat.

OpenAI's current developer guide documents the custom MCP connection flow and its OAuth requirements. We plan to submit the official Scene Dept. plugin after the public beta deployment and production OAuth flow pass their launch checks.

Connect from Claude

For an individual Claude account:

Open Customize, then Connectors.
Select Add custom connector.
Enter https://www.scenedept.com/mcp.
Leave optional OAuth client ID and client secret fields blank. Scene Dept. supports automatic client registration.
Select Connect, sign in to Scene Dept., and review the consent screen.

Team and Enterprise workspaces may require an owner to add the connector in organization settings before members can connect. See Anthropic's current remote MCP connector guide.

Choose access carefully

The Scene Dept. consent screen asks you to choose:

Read only: inspect projects and production plans without changing them.
Read and edit: use the approved write tools, including production edits and other actions described on the consent screen.
Selected projects: restrict the connection to projects you choose.
All accessible projects: include current and future projects you can access, plus supported team and account-level workflows.

Scene Dept. checks both the OAuth grant and your live project or team permissions on every tool call. Losing project access, leaving a team, disabling the account, or revoking the connection removes the corresponding MCP access. Existing grants never gain newly added capabilities silently; reconnect and review the new consent when required.

Manage or revoke connections

Open Account settings or a project's MCP setup page to see connected assistants, their project scope, access level, expiration date, and last use. Select Revoke access to disable a grant. You can also disconnect the connector in the assistant's settings.

OAuth connections expire after 90 days. The assistant can refresh its short-lived access while the grant remains valid. If a connection stops working after an access or capability change, remove it from the assistant and connect again.

Legacy manual Scene Dept. bearer tokens are no longer accepted. Create a new OAuth connection instead.

Privacy and safety

Connect only through https://www.scenedept.com/mcp.
Review the assistant's requested access and the Scene Dept. consent screen.
Prefer read-only and selected-project access when broader access is unnecessary.
Ask the assistant to explain proposed edits before applying them.
Revoke unfamiliar or unused connections.
Treat temporary visual-note image links as private.

The external assistant provides the model inference. Its service terms, data controls, and model charges are separate from Scene Dept. and do not consume a future Scene Dept. AI allowance.

Try a first request

After enabling the connector in a conversation, try:

Read my Scene Dept. project and summarize the scenes, shots, setups, and any obvious coverage gaps. Ask before making changes.

If the assistant cannot connect, confirm that the URL ends in /mcp, the connector supports OAuth and Streamable HTTP, your Scene Dept. account is verified and enabled, and your assistant workspace permits custom connectors.