> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/intangible-mcp-agents/connect-cursor.md).

# Cursor

Intangible works with Cursor. Connect Cursor to Intangible's Model Context Protocol (MCP) server in mcp.json, then build 3D scenes from Cursor's Agent mode.

**Yes, Intangible works with Cursor.** Connect Cursor to Intangible's MCP server and its agent builds 3D scenes in your Studio tab.

## At a glance

| Setting          | Value                                                                                |
| ---------------- | ------------------------------------------------------------------------------------ |
| Server URL       | `https://mcp.intangible.ai/mcp`                                                      |
| Where you add it | `~/.cursor/mcp.json`, under `mcpServers`                                             |
| Sign-in          | **Connect** in Cursor's MCP settings, then **Approve access** on the Intangible page |
| Chat mode        | **Agent**. Ask mode can't call tools                                                 |

## Before you start

* An Intangible account. Sign up at [studio.intangible.ai](https://studio.intangible.ai/?utm_source=help.intangible.ai\&utm_medium=docs\&utm_campaign=inline-link\&utm_content=connect-cursor).
* Cursor, installed and signed in.

## Cursor: add the Intangible server

1. Open `~/.cursor/mcp.json` in a text editor. Create the file if it doesn't exist.
2. Add an `intangible` entry under `mcpServers`. If the file already lists other servers, add it alongside them:

   ```json
   {
     "mcpServers": {
       "intangible": {
         "url": "https://mcp.intangible.ai/mcp"
       }
     }
   }
   ```
3. Save the file and open Cursor's settings, then its MCP section.
4. Click **Connect** on **intangible**, then click **Approve access** on the Intangible page that opens.

## Cursor: build a scene

1. Open a project in Studio at [studio.intangible.ai](https://studio.intangible.ai/?utm_source=help.intangible.ai\&utm_medium=docs\&utm_campaign=inline-link\&utm_content=connect-cursor). Keep only that one Studio tab open.
2. Open Cursor's chat and set the mode to **Agent**.
3. To skip a confirmation on every step, turn on auto-run in Cursor's chat settings.
4. Ask Cursor to use the intangible MCP server, then [describe your first scene](/intangible-mcp-agents/intangible-mcp-agents.md#describe-your-first-scene).

## Related

* [Agents & MCP](/intangible-mcp-agents/intangible-mcp-agents.md)
* [Choosing a model](/intangible-mcp-agents/choosing-a-model.md)
* [Troubleshooting and FAQ](/intangible-mcp-agents/troubleshooting-and-faq.md)

*Last updated 23 October 2026. Steps may change.*


---

# 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://help.intangible.ai/intangible-mcp-agents/connect-cursor.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.