> 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-perplexity.md).

# Perplexity

Intangible works with Perplexity. Add Intangible's Model Context Protocol (MCP) server as a custom connector, then build 3D scenes from a Perplexity Computer task.

**Yes, Intangible works with Perplexity.** Add Intangible as a custom connector and Perplexity builds 3D scenes in your Studio tab as a Computer task.

## At a glance

| Setting          | Value                                                             |
| ---------------- | ----------------------------------------------------------------- |
| Server URL       | `https://mcp.intangible.ai/mcp`                                   |
| Where you add it | **Customize › Connectors › Custom connector › Add MCP connector** |
| Authentication   | OAuth                                                             |
| Transport        | Streamable HTTP                                                   |
| Approvals        | Perplexity asks before each step                                  |

## 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-perplexity).
* A Perplexity account that can add custom connectors.

## Perplexity: add Intangible as a custom connector

1. Go to **Customize › Connectors**.
2. Click **Custom connector**, then **Add MCP connector**.
3. Set the name to **Intangible** and the MCP server URL to `https://mcp.intangible.ai/mcp`.
4. Leave **Advanced** on its defaults: **Authentication** OAuth, **Transport** Streamable HTTP, **Network access** Public.
5. Tick **I understand custom connectors can introduce risks**, then click **Add**.

## Perplexity: sign in

1. Search the connectors for **Intangible** and open its card.
2. Click **Add connector**.
3. An Intangible page reads **Perplexity is requesting access to your Intangible account**. Click **Approve access**.

## Perplexity: 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-perplexity). Keep only that one Studio tab open.
2. In Perplexity, ask it to use the Intangible connector, then [describe your first scene](/intangible-mcp-agents/intangible-mcp-agents.md#describe-your-first-scene).
3. Perplexity runs the job as a Computer task and asks you to approve each step. Approve each one to keep the build moving.

## 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-perplexity.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.