Skip to main content
All examples use https://mcp.sia.vision/studio. Client settings, plan availability and organization restrictions can change. These are setup guides, not a claim of platform verification or complete workflow acceptance.

​
Codex

Add a remote HTTP server in Codex’s MCP settings, or use the CLI:
Keep an existing SIA server name when updating it. A private companion plugin may provide additional file/workflow helpers; it does not replace the OAuth connection or grant permissions by installation.

​
ChatGPT

Where custom remote MCP apps are enabled for your plan and workspace, create a custom app using the endpoint above, then follow SIA’s native authorization. Workspace administrators may need to enable the feature. SIA’s public directory package is being prepared; this is not a live directory listing.

​
Claude

Where custom connectors are available, add the endpoint in connector settings and authorize SIA. Claude Code can use:
The full SIA media-generation connector is subject to Anthropic’s directory policy restrictions. A custom connection is separate from directory eligibility. No verified listing or exception is claimed.

​
Copilot

In GitHub Copilot desktop, open Customize → Add → MCP Server, select HTTP, and enter the endpoint. Leave headers, OAuth client ID and callback port empty for the basic native discovery flow. Sign in and verify account and saved-work reads. VS Code uses a different configuration shape:
GitHub’s repository-level cloud agent and code-review settings have different OAuth support. Do not assume the desktop setup works there. Verified GitHub connector distribution is separate from custom MCP setup. For a deliberate desktop upload/authoring connection, Copilot’s public OAuth Client ID is https://github.com/copilot/desktop/client-metadata.json; request OAuth scopes account:read studio:read studio:write. Complete fresh native consent. Leave headers and callback port empty. This grant does not include generation or renewable access. Do not alter authorization URLs by hand.

​
Antigravity

Add the server to your workspace or user MCP configuration and complete native sign-in:
An Antigravity custom server is separate from a consumer Gemini Connected App. Upload and playback support must be checked in the actual client.

​
Gemini

SIA’s consumer Connected App is in compatibility and submission preparation. It is not currently a verified Gemini listing. Gemini CLI has a separate remote MCP setup; follow its current native OAuth instructions using the canonical endpoint. A CLI connection does not establish consumer Gemini availability.

​
Grok

Where your plan supports custom connectors, add the public MCP URL and follow native sign-in. Business workspaces may require administrator provisioning. Full SIA upload, media and write acceptance in Grok remains pending; start with account and saved-work reads.

​
Muse

The Meta Muse connector is in submission preparation. The public listing and verification have not been approved. Native attachment, media playback and sensitive-action handling require Muse-specific acceptance before broad workflow availability can be claimed.

​
Updating an existing connection

Keep the canonical endpoint and your current server key. Refresh the tool list or start a fresh chat after updates. Reconnect through native OAuth when permissions expire or change. Do not copy another host’s credentials, clear an uncertain operation to force another transfer, or confuse a local callback URL with the production endpoint.