> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-studio/integrations/ai-chat.md).

# AI chat (Claude, ChatGPT, Codex)

Marso MCP connects your AI agent to Marso Studio. Add it to Claude, ChatGPT, Codex or Claude Code, and ask the agent for 3D assets in a chat. It builds them on Marso Studio's node graph, in your own account.

## What you'll need

* An agent that can use MCP connectors: Claude, ChatGPT, Codex or Claude Code.
* A paid plan or the trial. Marso MCP works through the Marso Studio API, which the Free plan doesn't include, and a key made during the trial stops working when the trial ends. See [Plans](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md#plans).
* An API key: step 1 below.

## 1. Create an API key

1. Log in to [marso.app](https://marso.app/).
2. Open **API Keys** in the left sidebar.
3. Under **New Key**, give the key a name ("Claude" or "ChatGPT", say) and click **Create Key**.
4. **Copy the key straight away.** It's shown only once.

## 2. Add Marso MCP to your agent

Marso MCP is one URL. Add it to your agent as a connector:

```
https://mcp.api.marso.app/mcp
```

Add it with the URL only. Don't put your API key in the connector's settings or headers: you paste it once, when you first sign in.

### Claude

1. In Claude, on the web or in the desktop app, open **Settings**, then **Connectors**, and choose **Add custom connector**.
2. Name it Marso and paste the server URL. Under **Authentication**, choose **Sign in when needed**, and leave **Request headers** empty. Claude may say "Detected: No sign-in". That's expected: Marso MCP asks you to sign in when your agent first uses it.
3. In a chat, turn on Marso from the tools menu and ask for an asset.

On a Team or Enterprise plan, an owner adds the connector first, in **Admin settings**.

### ChatGPT

1. Open **Settings**, then **Apps & Connectors**, then **Advanced settings**, and turn on **Developer mode**.
2. Back in **Apps & Connectors**, choose **Create**. Name it Marso, paste the server URL and pick **OAuth**.
3. In a new chat, add Marso from the **+** menu and ask for an asset. A chat you started before adding the connector won't pick it up.

Developer mode depends on your ChatGPT plan. In a workspace, an admin may need to turn it on first.

### Codex

1. Run:

   ```
   codex mcp add marso --url https://mcp.api.marso.app/mcp
   ```
2. Run `codex mcp login marso`. Your browser opens to sign in.
3. Start a Codex session and ask for an asset.

The Codex IDE extension reads the same settings, so you add the server once.

### Claude Code

1. Run:

   ```
   claude mcp add --transport http marso https://mcp.api.marso.app/mcp
   ```
2. In Claude Code, run `/mcp` and pick **marso** to sign in.
3. Ask for an asset. Claude Code can upload images and 3D models from your computer for you.

## 3. Sign in the first time

The first time your agent uses Marso, it asks you to sign in:

1. **Sign in to Marso MCP.** This is its own sign-in, separate from your marso.app login: sign up with an email, or continue with Google.
2. **Paste your Marso Studio API key** and click **Connect**. Marso checks the key before it saves it.

The key is what links Marso MCP to your Marso Studio account. Everything your agent makes goes into the account the key belongs to, and spends that account's credits. The key is stored encrypted, and it never passes through the chat.

Each Marso MCP sign-in holds one key. If several people share one sign-in, all their work lands in one Marso Studio account, so each person should sign in as themselves, with their own key.

### Changing or removing your key

Go to [mcp.api.marso.app/link](https://mcp.api.marso.app/link), sign in, and choose **Replace key** or **Remove linked key**. Your agent picks up the change on its next call.

If you revoke a key in Marso Studio, create a new one and link it.

## What your agent can do

* Generate images of single objects or whole scenes, and edit images with a prompt.
* Detect the objects in a scene image, and let you choose which ones to keep.
* Turn images into 3D models, and give them predicted PBR materials.
* Give predicted PBR materials to 3D models you upload.
* Change the textures of a 3D model with a prompt.
* Work across many objects at once, such as every object in a scene.
* Open and add to your projects, browse your Library, show results in the chat, and give you download links.
* Work in your open Blender or Isaac Sim through the Marso add-ons. See [Your agent in Blender and Isaac Sim](#your-agent-in-blender-and-isaac-sim).

## Where your work goes

Your agent works in your Marso Studio projects, the same ones you open at [marso.app](https://marso.app/). It uses the project you're working on, or starts a new one named after what you asked for. Open the project any time to check what the agent did and carry on by hand. What it makes on a project shows in your Library too: see [Library & collections](https://docs.m-xr.com/marso-studio/reference/library-and-collections.md).

Your agent can add nodes to a project and connect them, but it can't delete a project or a node.

## Credits

Marso MCP spends credits from your Marso Studio balance, at the same prices as the app. See [Credits & billing](https://docs.m-xr.com/marso-studio/reference/credits-and-billing.md).

Before a larger step, your agent checks the price against your balance, and by default it asks you first. You can tell it how much it may spend without asking ("go ahead, up to 500 credits"), give it a standing allowance, or tell it to run straight through. These are instructions your agent follows. Marso charges each run what it costs.

## Your own files

Marso MCP runs online, so it can't open files on your computer. To use your own image or 3D model, your agent gives you an upload link. Drop the file on that page, then go back to the chat: the agent carries on by itself. Claude Code can upload files from your computer for you. See [Marso MCP troubleshooting](https://docs.m-xr.com/marso-studio/integrations/ai-chat/marso-mcp-troubleshooting.md) for file types and sizes.

## Your agent in Blender and Isaac Sim

With the Marso add-on connected, your agent can work in your open Blender or Isaac Sim as well as in Marso Studio. It makes the assets in Marso Studio, and the add-on brings them into your scene or onto your stage. No file passes through the chat.

### What your agent can do there

**In Blender:**

* Build new models in your scene, when you add Blender's own MCP server too. That route doesn't need Marso MCP at all: see [Blender](https://docs.m-xr.com/marso-studio/integrations/blender.md), part 2.
* Put Marso assets into your scene: new ones it makes, or ones already in your Library.
* Give meshes already in your scene predicted PBR materials.
* Use what your scene shows, such as a blockout or a render, as the starting point for new assets.
* Set up a product studio, animate a turntable or a showcase, and render stills or videos, which it shows you in the chat.

**In Isaac Sim:**

* Put Marso assets on your stage as USD, at real-world size and with physics: new ones it makes, or ones already in your Library.
* Film them in Sim Studio, dropping, sliding, in wind, colliding or picked up by a robot, and show you the video in the chat.

If both apps are connected and you don't say which one you mean, your agent asks.

### Connecting them

|              | Blender                                                                                                          | Isaac Sim                                                                                      |
| ------------ | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| The add-on   | Set up as in [Blender](https://docs.m-xr.com/marso-studio/integrations/blender.md), part 1                       | Set up as in [Isaac Sim](https://docs.m-xr.com/marso-studio/integrations/isaac-sim.md), part 1 |
| Switch on    | **Edit → Preferences → Add-ons → Marso**, then **Connect to Marso Agents** under **Advanced → Agent Connection** | **Connect to Marso Agents** under **Settings → Agent connection** in the Marso window          |
| When it's on | The Marso panel shows **Agents connected as** your email                                                         | The Settings tab shows **Connected as** your email                                             |

The add-on's API key doesn't have to be the one your agent uses, but it must belong to the same Marso Studio account: that's how your agent finds your Blender or Isaac Sim. One Blender and one Isaac Sim can be connected to an account at a time. Connecting a second Blender takes over from the first.

### What stays in your hands

The add-ons connect out to Marso with your API key. Through them, your agent can't:

* change the add-on's settings, its API key or its folders
* open, read or upload files on your computer
* run code
* use the add-on's own Create 3D Asset panel in Blender, or the Create tab in Isaac Sim
* run Retexture in Blender. Through Blender's own MCP server it can: see [Building with your agent](https://docs.m-xr.com/marso-studio/integrations/blender/building-with-your-agent.md).

To model in Blender, your agent uses Blender's own MCP server, which does run the code your agent writes. See [Blender](https://docs.m-xr.com/marso-studio/integrations/blender.md), part 2.

In Blender, your agent can clear the scene of Blender's default objects and of everything Marso added to it.

### Credits in Blender and Isaac Sim

Making new assets costs what it costs in Marso Studio. Giving meshes in your Blender scene PBR materials also spends credits, and your agent has to get a quote first. Everything your agent does in Isaac Sim is free, Sim Studio included: it runs on your computer.

### Renders and videos

Renders from Blender and videos from Sim Studio come back to the chat as a link, up to 50 MB. The link works for a day, and anyone who has it can view the file for that day. To see one again after that, ask your agent to send it again.

Something not working? See [Marso MCP troubleshooting](https://docs.m-xr.com/marso-studio/integrations/ai-chat/marso-mcp-troubleshooting.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.m-xr.com/marso-studio/integrations/ai-chat.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
