> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/consume-with-ai/connect-clients/codex-desktop.md).

# Codex Desktop

Connecting Codex Desktop to Data Product MCP lets it answer your data questions from governed Data Products instead of guessing — configure it once in the MCP Servers settings to give Codex trusted, authorized data.

From the Data Product page, select **Activate → MCP**, then select **View install guide** on the **Codex Desktop** card to open the step-by-step guide.

![Codex Desktop install guide showing the MCP server values](/files/FaPq7uwFiW7nawbccWv8)

## Prerequisites

You need:

* Codex Desktop installed.
* Your DataOS instance URL, such as `pacific-051426.dataos.cloud`.
* A DataOS API token generated from [Home → Generate API tokens](/consume/get-started/readme-1.md#get-a-dataos-api-token).

## Steps

### 1. Open MCP servers

Open **Codex Settings** and click **MCP Servers**.

### 2. Add the Data Product MCP server

Add a new MCP server with the following values, replacing `<instance-url>` and `<API_TOKEN>` with your values.

| Field        | Value                                           |
| ------------ | ----------------------------------------------- |
| Name         | `DataProduct-MCP`                               |
| URL          | `https://<instance-url>/dataproduct-mcp/api/v1` |
| Header key   | `apikey`                                        |
| Header value | `<API_TOKEN>`                                   |

### 3. Save and verify

Save the server and confirm **DataProduct-MCP** appears in the MCP Servers list. Then ask:

```
What data products are available to consume?
```

Codex should return Data Products from your DataOS instance, scoped to your token permissions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/consume/consume-with-ai/connect-clients/codex-desktop.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.