Setup guide

Connect Switch to your AI.

Switch runs a hosted MCP server. There is nothing to install and no server to run. Add one endpoint to your AI client, sign in once, and it can browse your library, check your balance, and create images and video right from the chat.

The only endpoint you need

https://www.switchapp.ai/mcp

Use this exact URL in every client below. It is both this website and the machine endpoint. Your browser sees a page, your AI client sees the MCP server.

Pick your client.

Every one of these connects to the same endpoint. Choose yours and jump to its steps.

Claude on the web
The fastest setup. One custom connector, sign in once.
Claude Desktop
Native connector. No bridge, no terminal.
Claude Code (CLI)
Add once at user scope, then sign in inside a session.
Codex (CLI)
Native remote MCP with OAuth. Use one canonical connection only.
Kimi Code (Kimi 3 and Kimi 2)
One MCP connection works with every Kimi model selected in Kimi Code.
Gemini CLI
Native remote HTTP MCP with automatic OAuth discovery.
Cursor
Add an HTTP MCP server, for every project or for one.
Grok (grok.com and Grok Bot)
Custom connector on grok.com. Grok Bot cannot open a browser, so it uses a Switch API key.
ChatGPT connector
Requires a paid ChatGPT plan with Developer mode enabled.
Muse (Meta)
Ask Muse to create a Custom Connector for Switch.
DeepSeek models
DeepSeek is a model API, not a remote MCP client by itself.
BytePlus Managed Agent
Attach Switch as an MCP server plus the MCP toolset in a Managed Agent.

Inside Adobe.

Two free panels put the same brain inside the apps you already edit in. Each has its own page with the download and the steps.

How signing in works.

Switch uses the standard sign in handshake, called OAuth. Your client never sees your Switch password. After you add the endpoint, the first time your AI uses a Switch tool it opens a Switch sign in page in your browser. Approve access, and your client keeps a key that renews quietly from then on. There is no API key to copy for the connector. Signing in is the only door.

The one trick that fixes most sign in problems

Do not close the tab that says it cannot load.

After you approve access, the browser tab may show a “can’t reach localhost” or “MCP CLI Proxy” error. Copy the entire URL from the address bar. It looks like http://localhost:PORT/callback?code=…&state=… Paste it back to your assistant or client to finish login. The page failing to load is normal in remote or sandboxed sessions. The code in that URL is still valid.

Set up your client.

Claude on the web

The fastest setup. One custom connector, sign in once.

1
In the claude.ai sidebar open Customize, then Connectors. Anthropic moved this out of Settings. If a guide says "Settings → Connectors", it now lives under Customize → Connectors.
2
Click Add, then Add custom connector.
3
Name it Switch and paste the endpoint as the Remote MCP server URL:
Remote MCP server URL
```
https://www.switchapp.ai/mcp
```
4
Click Add, then Connect. A Switch sign in page opens. Sign in with your Switch account and click Allow.
5
Done. The connector shows a checkmark and lists the Switch tools. Ask Claude "use switch to list my images" to confirm.

Claude Desktop

Native connector. No bridge, no terminal.

1
Easiest: Settings → Connectors → Add custom connector, set the URL below and type HTTP, then Save and Connect.
Server URL
```
https://www.switchapp.ai/mcp
```
2
No "Add custom connector" button? Edit the config file instead and restart Claude Desktop:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
```
{
  "mcpServers": {
    "switch": { "type": "http", "url": "https://www.switchapp.ai/mcp" }
  }
}
```
3
When it asks you to sign in, complete the browser OAuth step (see "How signing in works" above). Avoid the npx mcp-remote bridge. Use the native HTTP connector above.

Claude Code (CLI)

Add once at user scope, then sign in inside a session.

Add the server (user scope makes it available in every project):

Terminal

claude mcp add --transport http -s user switch https://www.switchapp.ai/mcp

2
Start a session and trigger a Switch tool. Claude Code opens the browser for the OAuth sign in.
3
Confirm it connected:
Terminal. Expect: switch ✔ Connected
```
claude mcp list
```
4
Need a clean slate? Remove it with:
Terminal
```
claude mcp remove switch
```

Codex (CLI)

Native remote MCP with OAuth. Use one canonical connection only.

Add Switch using Codex’s MCP command:

Terminal

codex mcp add switch --url https://www.switchapp.ai/mcp

2
Complete Switch OAuth, then restart Codex:
Terminal
```
codex mcp login switch
```
3
Confirm the Switch row says enabled and OAuth:
Terminal
```
codex mcp list
```

Kimi Code (Kimi 3 and Kimi 2)

One MCP connection works with every Kimi model selected in Kimi Code.

Add Switch to the user level Kimi MCP file:

~/.kimi-code/mcp.json

{
  "mcpServers": {
    "switch": { "url": "https://www.switchapp.ai/mcp" }
  }
}

2
Start Kimi Code and run /mcp-config login switch. Complete the Switch sign in in the browser.
3
Run /mcp to confirm Switch is connected. Changing between Kimi 3 and Kimi 2 does not change the MCP connection.

Gemini CLI

Native remote HTTP MCP with automatic OAuth discovery.

Add Switch at user scope:

Terminal

gemini mcp add --scope user --transport http switch https://www.switchapp.ai/mcp

2
Start Gemini CLI and run /mcp auth switch. Complete the Switch sign in in the browser.
3
Confirm it is available:
Terminal
```
gemini mcp list
```

Cursor

Add an HTTP MCP server, for every project or for one.

1
Add Switch to your Cursor MCP config: ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside one project:
~/.cursor/mcp.json
```
{
  "mcpServers": {
    "switch": { "url": "https://www.switchapp.ai/mcp" }
  }
}
```
2
Open Cursor → Settings → MCP, enable Switch, and sign in with your Switch account (OAuth) when prompted.

Grok (grok.com and Grok Bot)

Custom connector on grok.com. Grok Bot cannot open a browser, so it uses a Switch API key.

1
On grok.com open Connectors, click New Connector, then Custom.
2
Paste the Switch MCP server URL:
MCP server URL
```
https://www.switchapp.ai/mcp
```
3
Grok web: finish the sign in it shows you (OAuth), that is your Switch account login.
4
Grok Bot and other bots that cannot open a browser: create a key on the Switch Developer page (www.switchapp.ai/developer, API keys, Create key) and give it to the bot as the Bearer token for the same URL. Keys made there carry the MCP scopes.
Header the bot sends
```
Authorization: Bearer sk_switch_live_...
```
5
Grok then lists the Switch tools and can generate, upload, search your library and check your balance on your account.

ChatGPT connector

Requires a paid ChatGPT plan with Developer mode enabled.

1
In ChatGPT, open Settings → Connectors → Advanced, and turn on Developer mode (needed for custom MCP servers).
2
Back in Connectors, choose Create / Add custom connector.
3
Name it Switch, set the MCP server URL below, and choose OAuth for authentication:
MCP server URL
```
https://www.switchapp.ai/mcp
```
4
Save, then open the connector in a chat and sign in with your Switch account when prompted.

Muse (Meta)

Ask Muse to create a Custom Connector for Switch.

1
Ask Muse to create a Custom Connector for Switch. Meta: “Muse will guide you through the process, which can involve retrieving API information from the service.” The information it needs from Switch is this address:
The Switch endpoint (Meta Help Center: “How Muse works with Connectors”)
```
https://www.switchapp.ai/mcp
```
2
Meta: “By default, Muse will not take many important actions, such as sending an email, without your approval.” Approve a Switch action when Muse asks.
3
Meta: “You can disconnect a Connector at any time in Settings under Connectors.”

DeepSeek models

DeepSeek is a model API, not a remote MCP client by itself.

1
Run DeepSeek inside an MCP capable agent such as Kimi Code or Claude Code, then add Switch to that client using the instructions above.
2
Do not paste the Switch MCP URL into the DeepSeek API. DeepSeek exposes function calling; the surrounding agent discovers and executes MCP tools.

BytePlus Managed Agent

Attach Switch as an MCP server plus the MCP toolset in a Managed Agent.

1
In ModelArk Managed Agents, register the canonical Switch URL as the agent’s MCP server. If OAuth is required, create the MCP OAuth credential in the agent vault.
2
Keep the default agent toolset and add the MCP toolset. Replacing the whole tool array with only the MCP toolset removes the agent’s normal tools.
3
Read the agent back after saving and confirm both the Switch MCP server and MCP toolset are present before running a read only Switch call.

Troubleshooting.

Open the line that matches what you see.

This was a bug on our side, fixed on July 15, 2026. If you still see the loop: remove the Switch connector in Claude, wait one minute, add it again with the exact URL https://www.switchapp.ai/mcp, and sign in once. Claude keeps a short memory of the old broken answer, which is why the one minute wait matters. If it still loops after that, contact support and tell us the time you tried.

Error -32001 / "Unauthorized"

Switch returns JSON-RPC -32001 with the message "Unauthorized" when a tool call needs sign in. Complete the OAuth login. Note: some clients also show -32001 for their own request timeouts, so check the message text: "Unauthorized" means sign in; "timed out" means wait a moment and retry a small call (like list or balance).

It says the token expired / "requires re-authorization"

A session that started with an old token keeps failing every call. Run the connect and sign in flow again to get a fresh token, then fully quit and reopen your client so it loads the new token.

Connector is stuck. Only "Disconnect" shows, no "Reconnect"

Disconnect (or remove the server), add it again with the same URL, sign in again, and restart the client. Key gotcha: a running session will not pick up a token you refreshed in another window. After signing in again, fully restart the client so it loads the new token.

For CLI and bridge setups, clear the cached auth: rm -rf ~/.mcp-auth on macOS and Linux, or delete %USERPROFILE%\.mcp-auth on Windows, then restart and sign in again. Native desktop connectors manage their own tokens internally, so for those just remove and add the connector again rather than hunting for files.

I see the tools but every call fails

Listing the tools needs no login (that is why you can see them). The first tool CALL is what triggers the sign in prompt. Complete the OAuth login and retry.

Tools never appear after adding the server

Check the URL is exactly https://www.switchapp.ai/mcp, that you restarted the client after editing any config file, and that the config file is valid JSON or TOML (a stray comma silently disables every server). Then try a lightweight call like check balance first.

Request timed out

A timeout means the request reached the server but no answer came back in time. It is not an auth failure. For big jobs (image or video), the job usually keeps running on Switch, so ask to show your last image or list your recent generations instead of firing the slow call again. For quick calls (list or balance), wait a minute and try one lightweight call first; check that the Switch website itself loads in a browser; and avoid hammering retries, each one just burns time.

Still stuck after a clean restart, fresh sign in, and cleared cache

Run the first check: the URL is exactly https://www.switchapp.ai/mcp, you restarted the client after any config change, and the config file is valid JSON or TOML (one stray comma silently disables every server). If all of that is true and it still fails, the problem is likely on the server side. Check Switch status and contact support; no client config can fix an unreachable server.

One address. Always.

Several addresses reach the server, but always use this one.

https://www.switchapp.ai/mcpThe one to use
Paste this one into every client. Verified live as a working connector.
Older addressesDo not use
A few older addresses still answer the server, but do not use them. Always paste the one address above.

Connect Switch to your AI.

The only endpoint you need

https://www.switchapp.ai/mcp

Use this exact URL in every client below. It is both this website and the machine endpoint. Your browser sees a page, your AI client sees the MCP server.

How signing in works.

The one trick that fixes most sign in problems

Do not close the tab that says it cannot load.

Set up your client.

Claude on the web

The fastest setup. One custom connector, sign in once.

1
In the claude.ai sidebar open Customize, then Connectors. Anthropic moved this out of Settings. If a guide says "Settings → Connectors", it now lives under Customize → Connectors.
2
Click Add, then Add custom connector.
3
Name it Switch and paste the endpoint as the Remote MCP server URL:
Remote MCP server URL
```
https://www.switchapp.ai/mcp
```
4
Click Add, then Connect. A Switch sign in page opens. Sign in with your Switch account and click Allow.
5
Done. The connector shows a checkmark and lists the Switch tools. Ask Claude "use switch to list my images" to confirm.

Claude Desktop

Native connector. No bridge, no terminal.

1
Easiest: Settings → Connectors → Add custom connector, set the URL below and type HTTP, then Save and Connect.
Server URL
```
https://www.switchapp.ai/mcp
```
2
No "Add custom connector" button? Edit the config file instead and restart Claude Desktop:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
```
{
  "mcpServers": {
    "switch": { "type": "http", "url": "https://www.switchapp.ai/mcp" }
  }
}
```
3
When it asks you to sign in, complete the browser OAuth step (see "How signing in works" above). Avoid the npx mcp-remote bridge. Use the native HTTP connector above.

Claude Code (CLI)

Add once at user scope, then sign in inside a session.

Add the server (user scope makes it available in every project):

Terminal

claude mcp add --transport http -s user switch https://www.switchapp.ai/mcp

2
Start a session and trigger a Switch tool. Claude Code opens the browser for the OAuth sign in.
3
Confirm it connected:
Terminal. Expect: switch ✔ Connected
```
claude mcp list
```
4
Need a clean slate? Remove it with:
Terminal
```
claude mcp remove switch
```

Codex (CLI)

Native remote MCP with OAuth. Use one canonical connection only.

Add Switch using Codex’s MCP command:

Terminal

codex mcp add switch --url https://www.switchapp.ai/mcp

2
Complete Switch OAuth, then restart Codex:
Terminal
```
codex mcp login switch
```
3
Confirm the Switch row says enabled and OAuth:
Terminal
```
codex mcp list
```

Kimi Code (Kimi 3 and Kimi 2)

One MCP connection works with every Kimi model selected in Kimi Code.

Add Switch to the user level Kimi MCP file:

~/.kimi-code/mcp.json

{
  "mcpServers": {
    "switch": { "url": "https://www.switchapp.ai/mcp" }
  }
}

2
Start Kimi Code and run /mcp-config login switch. Complete the Switch sign in in the browser.
3
Run /mcp to confirm Switch is connected. Changing between Kimi 3 and Kimi 2 does not change the MCP connection.

Gemini CLI

Native remote HTTP MCP with automatic OAuth discovery.

Add Switch at user scope:

Terminal

gemini mcp add --scope user --transport http switch https://www.switchapp.ai/mcp

2
Start Gemini CLI and run /mcp auth switch. Complete the Switch sign in in the browser.
3
Confirm it is available:
Terminal
```
gemini mcp list
```

Cursor

Add an HTTP MCP server, for every project or for one.

1
Add Switch to your Cursor MCP config: ~/.cursor/mcp.json for all projects, or .cursor/mcp.json inside one project:
~/.cursor/mcp.json
```
{
  "mcpServers": {
    "switch": { "url": "https://www.switchapp.ai/mcp" }
  }
}
```
2
Open Cursor → Settings → MCP, enable Switch, and sign in with your Switch account (OAuth) when prompted.

Grok (grok.com and Grok Bot)

Custom connector on grok.com. Grok Bot cannot open a browser, so it uses a Switch API key.

1
On grok.com open Connectors, click New Connector, then Custom.
2
Paste the Switch MCP server URL:
MCP server URL
```
https://www.switchapp.ai/mcp
```
3
Grok web: finish the sign in it shows you (OAuth), that is your Switch account login.
4
Grok Bot and other bots that cannot open a browser: create a key on the Switch Developer page (www.switchapp.ai/developer, API keys, Create key) and give it to the bot as the Bearer token for the same URL. Keys made there carry the MCP scopes.
Header the bot sends
```
Authorization: Bearer sk_switch_live_...
```
5
Grok then lists the Switch tools and can generate, upload, search your library and check your balance on your account.

ChatGPT connector

Requires a paid ChatGPT plan with Developer mode enabled.

1
In ChatGPT, open Settings → Connectors → Advanced, and turn on Developer mode (needed for custom MCP servers).
2
Back in Connectors, choose Create / Add custom connector.
3
Name it Switch, set the MCP server URL below, and choose OAuth for authentication:
MCP server URL
```
https://www.switchapp.ai/mcp
```
4
Save, then open the connector in a chat and sign in with your Switch account when prompted.

Muse (Meta)

Ask Muse to create a Custom Connector for Switch.

1
Ask Muse to create a Custom Connector for Switch. Meta: “Muse will guide you through the process, which can involve retrieving API information from the service.” The information it needs from Switch is this address:
The Switch endpoint (Meta Help Center: “How Muse works with Connectors”)
```
https://www.switchapp.ai/mcp
```
2
Meta: “By default, Muse will not take many important actions, such as sending an email, without your approval.” Approve a Switch action when Muse asks.
3
Meta: “You can disconnect a Connector at any time in Settings under Connectors.”

DeepSeek models

DeepSeek is a model API, not a remote MCP client by itself.

1
Run DeepSeek inside an MCP capable agent such as Kimi Code or Claude Code, then add Switch to that client using the instructions above.
2
Do not paste the Switch MCP URL into the DeepSeek API. DeepSeek exposes function calling; the surrounding agent discovers and executes MCP tools.

BytePlus Managed Agent

Attach Switch as an MCP server plus the MCP toolset in a Managed Agent.

1
In ModelArk Managed Agents, register the canonical Switch URL as the agent’s MCP server. If OAuth is required, create the MCP OAuth credential in the agent vault.
2
Keep the default agent toolset and add the MCP toolset. Replacing the whole tool array with only the MCP toolset removes the agent’s normal tools.
3
Read the agent back after saving and confirm both the Switch MCP server and MCP toolset are present before running a read only Switch call.

Troubleshooting.

Open the line that matches what you see.

Error -32001 / "Unauthorized"

It says the token expired / "requires re-authorization"

A session that started with an old token keeps failing every call. Run the connect and sign in flow again to get a fresh token, then fully quit and reopen your client so it loads the new token.

Connector is stuck. Only "Disconnect" shows, no "Reconnect"

I see the tools but every call fails

Listing the tools needs no login (that is why you can see them). The first tool CALL is what triggers the sign in prompt. Complete the OAuth login and retry.

Tools never appear after adding the server

Request timed out

Still stuck after a clean restart, fresh sign in, and cleared cache

One address. Always.

Several addresses reach the server, but always use this one.

https://www.switchapp.ai/mcpThe one to use

Paste this one into every client. Verified live as a working connector.

Older addressesDo not use

A few older addresses still answer the server, but do not use them. Always paste the one address above.