---
title: "Use in Claude or ChatGPT on the web"
description: "From Claude or ChatGPT in a browser or on a phone, you can make a game or app with KUMODeck and put it online."
url: "/docs/claude-and-chatgpt/"
lang: en
index: "/llms.txt"
---
# Use in Claude or ChatGPT on the web

From Claude or ChatGPT in a browser or on a phone, you can make a game or app with KUMODeck and put it online. You do not need files or commands on your computer: the conversation is enough.

- "Make a boat racing game in Three.js that people can play together online. Use KUMODeck."
- "Change the colors of that game and put it up again."
- "Publish it so everyone can play." (Before it goes out, you press a button to confirm.)

First, connect KUMODeck to Claude, ChatGPT or Muse once.

> These steps connect **KUMODeck Preview (v0.2)**: the usual tools plus 3D, Blender and images. Anyone with a KUMODeck account can connect it. These are new features we're still testing, and they may change.
>
> - Your AI makes a 3D character or object (about $0.20 each), makes heavy models lighter in Blender (about $0.01), and puts them in your game.
> - It can also make pictures like textures and backgrounds (from $0.003 each).
> - The cost comes out of your prepaid balance. If it is too low, your AI stops before making anything.

## Let the AI guide you

Copy this text and paste it into Claude, ChatGPT or Muse. The AI writes the setup steps in one message, one list for the first time and one if you added it before. When you have done them all, send "done": the AI checks the connection with projects_list. You do not need a browser extension. The same text works in Claude Code, Codex, Cursor and other AI agents on your computer.

```text Prompt to paste
Connect KUMODeck Preview (v0.2): if you can run commands here, run `npx kumodeck@latest connect --api https://api.kumodeck.com` (show me the link it prints and wait). If you can't, read https://kumodeck.com/docs/claude-and-chatgpt/index.md and do what it says (URL https://mcp-staging.kumodeck.com/mcp). Then make a small game with KUMODeck and publish it.
```

Some AI apps show their **own** confirmation screen, such as allowing a connection or sharing your chats and memory. Press its Connect or Allow button yourself. That screen comes from your AI app, not from KUMODeck.

Or follow the steps with pictures below.

## Before you start

- **A KUMODeck account.** Sign in or sign up at https://dashboard.kumodeck.com.
- **A computer browser.** Add KUMODeck on claude.ai or chatgpt.com in a browser (for Claude, the desktop app works too). The phone apps cannot add it.
- **The connection URL:** `https://mcp-staging.kumodeck.com/mcp`
- **On the KUMODeck page, keep Build and publish (recommended).** That choice lets the AI make and publish for you; publishing to everyone and deleting still ask you first.
- **Two tabs.** Keep the conversation open in one tab and open each settings page in a new tab (Cmd-click on a Mac, Ctrl-click on Windows). Opening it in the same tab hides the conversation.

What each Claude plan can do:

| Claude plan | Adding KUMODeck |
|---|---|
| Free | One custom connector. If you already have one, remove it first (**⋯** → **Remove**). |
| Pro, Max | Add it yourself. |
| Team, Enterprise | An Owner adds it for the organization. Members press **Connect**. |
| Phone app | Add it in a browser. Then it works in the phone app too. |

In ChatGPT, whether you can add a custom MCP server depends on your plan and may change. Work and school accounts need the admin to allow it. If you cannot find **Add custom MCP server**, see [If "Add custom MCP server" is not there](#if-add-custom-mcp-server-is-not-there).

## Connect in Claude

These steps are for the Free, Pro and Max plans. Team and Enterprise are [below](#claude-team-and-enterprise).

### 1. Open Customize → Connectors

Go to **Customize** → **Connectors** ([https://claude.ai/customize/connectors](https://claude.ai/customize/connectors)). Press **+ Add**, then **Add custom connector**.

### 2. Enter the name and the URL

Enter `KUMODeck Preview (v0.2)` as the name and `https://mcp-staging.kumodeck.com/mcp` as the **Remote MCP server URL**. Press **Continue**. If Claude asks how to sign in, keep the options that are already selected and press **Add**.

### 3. Sign in to KUMODeck and press Allow

The KUMODeck sign-in page opens (in the same tab on claude.ai, in your browser from the desktop app). Sign in, check what the AI may do, and press **Allow**. Back in Claude, KUMODeck Preview (v0.2) shows **Connected** under **Your connectors**.

### 4. Turn it on in a conversation

In a conversation, press **+** at the bottom left of the message box → **Connectors**, and turn on KUMODeck Preview (v0.2). Then ask, for example: "Make a small game with KUMODeck and publish it."

### Claude Team and Enterprise

Members cannot add a custom connector themselves.

1. An Owner opens **Organization settings** → **Connectors**, presses **Add**, points to **Custom** and chooses **Web**.
2. The Owner enters `KUMODeck Preview (v0.2)` and `https://mcp-staging.kumodeck.com/mcp`, presses **Continue**, keeps the sign-in options and presses **Add**.
3. Each member opens **Customize** → **Connectors**, finds KUMODeck Preview (v0.2) (marked **Custom**) and presses **Connect**, then signs in and presses **Allow**.

### Claude on a phone

Add KUMODeck on claude.ai in a browser (steps 1–3). The next time you open the Claude app on iOS or Android, KUMODeck Preview (v0.2) is there: turn it on in a conversation the same way.

## Connect in ChatGPT

Use chatgpt.com in a computer browser.

### 1. Open Plugins

Open **Plugins** in the left sidebar ([https://chatgpt.com/plugins](https://chatgpt.com/plugins)). Press **+**, then **Add custom MCP server**. (It may say **Create MCP App**.)

### 2. Enter the name and the URL

- Name: `KUMODeck Preview (v0.2)`
- **Server URL**: `https://mcp-staging.kumodeck.com/mcp`
- **Authentication**: **OAuth**

Tick **I understand and want to continue** and press **Create as a plugin**.

### 3. Install the plugin

Open KUMODeck Preview (v0.2) in your plugins ([https://chatgpt.com/plugins?view=personal](https://chatgpt.com/plugins?view=personal)) and press **+** to install it.

### 4. Sign in to KUMODeck and press Allow

The KUMODeck sign-in page opens. Sign in, check what the AI may do, and press **Allow**.

### 5. Pick it in a conversation

In the message box, type **@** and pick KUMODeck Preview (v0.2). Then ask, for example: "Make a small game with KUMODeck and publish it."

### If "Add custom MCP server" is not there

- Developer mode is usually not needed any more. If the button is missing, look for **Developer mode** in **Settings** → **Apps** → **Advanced settings** and turn it on.
- Work and school accounts: the admin must allow custom MCP servers.
- If your plan still cannot add one, Claude can be used instead (the Free plan allows one custom connector).

## Connect in Muse

Muse is Meta's AI agent ([Muse Help Center](https://www.meta.com/help/artificial-intelligence/1687253048996149/)). It adds KUMODeck as a **custom connector**. The same fields work in other AI apps that add an MCP server with OAuth.

### 1. Ask Muse to connect

Paste the text from [Let the AI guide you](#let-the-ai-guide-you) into Muse. Muse opens **Add custom connector**.

### 2. Enter the URL and the client ID, then press Add

```text Connection URL
https://mcp-staging.kumodeck.com/mcp
```

```text Client ID
kumodeck-muse
```

There is no client secret. This ID is not a password: it names "a connection from Muse" (after sign-in, it returns only to Muse).

Press **Add**. (Meta does not review custom connectors: you choose to add KUMODeck.)

Muse may also show **its own** screen that asks whether to allow a connection that shares related chats with KUMODeck (and memory, if memory is on). Muse does not let its AI press it: you press it yourself (we saw it once, in Japanese, with a **Connect** button; the English words and the button name may be different). This screen is from Muse, not from KUMODeck. Do not look for KUMODeck Preview (v0.2) in Muse's list of plugins: add it with the URL above.

### 3. Sign in to KUMODeck and press Connect

The KUMODeck page opens. Sign in, keep **Build and publish (recommended)** and press **Connect**. **This is the last button you press.** If you were connected before and KUMODeck asks for more, the button is **Allow**.

### 4. Use it from a new conversation

Muse may not see KUMODeck in the conversation where you connected it (it says it has no credentials yet). Start a new conversation in Muse and ask, for example: "Make a small game with KUMODeck and publish it." Muse can check the connection by listing your projects: that only reads and changes nothing.

### The names you will see

All of these are the same connection:

| Where | Name |
|---|---|
| The list of connectors | KUMODeck Preview (v0.2) |
| Commands and config files | `kumodeck-preview` |
| Tool names in some apps | the name with spaces and marks turned into `_` |
| The sign-in and permission page | KUMODeck |

## After KUMODeck is in the official lists

KUMODeck is being reviewed for Claude's connector directory and ChatGPT's plugin directory. Until it is listed, add it with the URL as above. Once it is listed:

- **Claude:** **Customize** → **Connectors** → **Discover**, search for KUMODeck and press **Connect to Claude**.
- **ChatGPT:** search for KUMODeck in **Plugins**, press **Install plugin**, then **Connect**.

What you add from a list connects the usual KUMODeck, not KUMODeck Preview (v0.2) (no 3D, Blender or image tools). To use KUMODeck Preview (v0.2), add it with the URL as above.

## Fewer "Allow this tool?" questions

Claude stops and asks "Allow this tool?" **the first time it uses each tool**. When you connect from Claude or ChatGPT on the web, there is **one tool (`publish_game`)** for making and publishing: setting up, sending the files, publishing and continuing after you press a button all go through it, so one "allow" usually takes you all the way.

To stop the questions, set the KUMODeck tools to "always allow".

### Always allow in Claude

- **In the conversation:** when Claude asks to use a tool, press **Always allow**. That tool will not ask again.
- **All at once:** in **Customize → Connectors**, select KUMODeck Preview (v0.2) and open **Tool permissions**. The tools are grouped into read-only tools and tools that make changes: choose **Always allow** for each (**Needs approval** = ask every time, **Blocked** = never use).
- On Team and Enterprise plans, the organization's admin sets these.

### Fewer questions in ChatGPT

ChatGPT checks with you every time before a tool makes a change. On that check, choose to **remember it for this conversation**: the same tool will not ask again in that conversation. There is no setting to never ask (a new conversation asks again).

### What you still press yourself

"Always allow" only stops Claude or ChatGPT from pausing. These still wait until **you** press a button in your browser:

- putting it on the address everyone can open, or replacing what is there (you press "Publish" on the KUMODeck confirmation page)
- adding a key for another service (you paste it into a small KUMODeck page, never into the conversation)

## Bigger games

You do not need to download anything, use a terminal or change a setting. What goes through the conversation depends on the size:

- **The code the assistant writes, and images and sounds it can write out itself**: the assistant sends them inside the conversation in parts and publishes the game. The assistant usually writes out about 100 KB per part, and one file has to go whole in one part (the tool takes up to about 4 MB per part); all parts together can be up to 20 MB and 1,000 files. Everything sent also stays in the conversation, so a game of a few MB takes many parts.
- **Big files (3D models, large images or sounds), files you attach, and big games**: the assistant gives you a link to KUMODeck's **upload page**. Open it and put the files there (up to 100 MB per file). Files you attach go this way because the assistant sends files by writing them out as text, and it cannot write out a file it did not make.

Claude's place for running code usually cannot send to KUMODeck directly: at first it can only reach a set list of places, such as package registries ([Claude Help Center](https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude)). That is why small games are sent in parts inside the conversation and big files go through the upload page, with no setting to change.

## If something goes wrong

- "Allow this tool?" keeps coming back → set "always allow" as above.
- You pressed the publish button but nothing moves → write "I pressed it" in the conversation and it continues.
- ChatGPT or Claude says it cannot use the KUMODeck tools, or that KUMODeck is not connected → add KUMODeck Preview (v0.2) again from the **+** in the message box (in Claude: **+** → **Connectors**, and turn KUMODeck Preview (v0.2) on again). Then ask again.
- How to fix errors is in [Talk to your AI agent](/docs/ask-claude-code/index.md); connecting other agents (Claude Code, Codex…) is in [Use from an AI agent (MCP)](/docs/claude-code/index.md).

## For the AI reading this page

The user pasted a short text that points here. When you give them the steps:

- If the text the user pasted gives a name and a URL, use those, not the values on this page.
- Sign-in is OAuth. It is not in any app's list of connectors: add it by URL (the URL on this page is https://mcp-staging.kumodeck.com/mcp). If Muse asks for a client ID, it is `kumodeck-muse`.
- If you can run commands and the command in the pasted text could not add it to your app, add it yourself (use the URL from the pasted text): Claude Code `claude mcp add --transport http kumodeck-preview https://mcp-staging.kumodeck.com/mcp`, Codex `codex mcp add kumodeck-preview --url https://mcp-staging.kumodeck.com/mcp`.
- Ask the user nothing; give the whole checklist in one message. Do not stop after each click to ask what the user sees. Do not ask the user to install a browser extension or turn on computer control. The user does the settings.
- Write two short checklists. A) First time: open the settings → add a custom connector → paste the name and URL → sign in to KUMODeck → keep "Build and publish (recommended)" and press Connect (or Allow). B) Already added before: open it in the same settings and press Reconnect. Do not add a second one. Do not disconnect.
- If your own app shows a confirmation screen (such as allowing the connection or sharing chats and memory), write in A that the user presses its button. Add that your app stops there, not KUMODeck.
- When the user says "done", check with projects_list (read only). Do not say it works until projects_list succeeds. If the tools are not in this conversation, tell the user to start a new conversation and try there.
- If "Authentication accepted. Please try again" appears twice, the user stops and tells you the exact message, the time (with time zone) and the step. Do not make them keep retrying.