Skip to main content

Connect Codex to DataDoe

Connect Codex to DataDoe to use your Amazon data while generating or changing code. You sign in to DataDoe during setup. You do not need a DataDoe MCP key for this connection.

The ChatGPT desktop app, the Codex CLI, and the IDE extension share this configuration.

Before you start

Use this server address exactly, with no extra slash at the end:

https://mcp.datadoe.com/mcp/v1

Codex sign-in works for that address only. If your Organization uses a white-label server address, connect with an MCP key instead.

Step 1: Add the DataDoe server

In a terminal, run:

bash
1codex mcp add datadoe --url https://mcp.datadoe.com/mcp/v1

You can add the same server in ~/.codex/config.toml. Codex also merges a project-level .codex/config.toml, but only in folders you have marked as trusted:

toml
1[mcp_servers.datadoe]
2url = "https://mcp.datadoe.com/mcp/v1"
3startup_timeout_sec = 30

Leave the OAuth callback settings at their defaults. A custom callback address will not be accepted.

Step 2: Sign in to DataDoe

  1. Run codex mcp login datadoe.
  2. Sign in with your DataDoe account for the Organization you want to use.
  3. Finish authorization and return to Codex.

In the Codex terminal, run /mcp and check that DataDoe is listed.

Step 3: Test the connection

Ask Codex:

Use DataDoe to list my connected Amazon accounts.

Then ask:

Use DataDoe to show my Amazon Seller Central sales for the last 7 days.

Name the Amazon account or marketplace if you manage more than one.

Connect with an MCP key instead

Use a DataDoe MCP key when you want a connection that does not depend on sign-in. This includes a white-label server address. Create a key in DataDoe MCP Integrations (opens in a new tab), then add it to ~/.codex/config.toml:

toml
1[mcp_servers.datadoe]
2url = "https://mcp.datadoe.com/mcp/v1"
3http_headers = { "datadoe-mcp-key" = "YOUR_DATADOE_MCP_KEY" }
4startup_timeout_sec = 30

Replace YOUR_DATADOE_MCP_KEY with your key. Keep the key in the home-level file, not in a shared project.

Restart your Codex session so it loads the key.

If you need help

If sign-in fails, check that the server address matches the address above and that you have not set a custom OAuth callback. Then run codex mcp login datadoe again.

If you use a white-label server address, remove the sign-in server and connect with an MCP key.

If Codex connects but returns no data, check your DataDoe Organization and Amazon connections, then ask Codex to use DataDoe explicitly.

Helpful resources


DataDoe MCP resources

Check the following resources for more information: