Connect Codex CLI

Connect Codex CLI to your Daasity data from Terminal - install, add the MCP server, sign in, and verify the connection.

Use Terminal, not Connections: This verified procedure is for Codex CLI. The Codex Desktop app’s Connections screen is for remote-device and SSH connections and is not where this MCP connection is configured.

Prerequisites: Access to Daasity AI Analyst and the MCP feature, plus a current version of Node.js and npm.

Privacy: The Daasity MCP URL is generated for your environment and account. Don't share it, and don't use a URL copied from another workspace or an example.

Steps to connect the MCP to your Codex CLI

1

Step 1 — Copy your Daasity MCP URL

In Daasity, open AI Analyst → Connect Your AI. Choose Codex, then copy the MCP server URL shown for your connection. Copy it directly from Daasity each time you configure a new connection.

2

Step 2 — Install Codex CLI

Open Terminal and run: npm install -g @openai/codex. Then confirm the installation with: codex --version. If Terminal reports “command not found: codex,” repeat the installation and open a new Terminal window.

3

Step 3 — Add Daasity as an MCP server

Run: codex mcp add daasity --url "<your Daasity MCP URL>". The word “daasity” is the local nickname. You may choose another nickname, but you must use that same name in later commands.

4

Step 4 — Sign in and approve the connection

Run: codex mcp login daasity. Your browser opens the Daasity authorization page. Confirm the correct workspace and read-only permissions, optionally name the connection, then select “Approve and connect.” Terminal should return: Successfully logged in to MCP server 'daasity'.

5

Step 5 — Create a safe test folder

Use an empty folder so you do not need to trust an existing project. Run: mkdir -p ~/daasity-mcp-test, then: cd ~/daasity-mcp-test.

6

Step 6 — Test semantic-view discovery

Run: codex --ask-for-approval on-request 'Use the Daasity MCP to list the available semantic views. Do not run a data query. Return only the view names.'

When Codex asks whether you trust ~/daasity-mcp-test, select “Yes, continue.” When it asks to run daasity.find_views, choose “Allow” for this single read-only call.

Connection checkpoint: If Codex returns semantic-view names, the MCP connection is working. This first test intentionally uses find_views without running a data query.

Ask a data question

After the view-list test succeeds, ask a clear, date-bounded question. Example: “Using the Daasity MCP, what are net sales from January 1, 2026 through September 4, 2026? Return the total and currency only.” Review the proposed daasity.query tool call and select Allow only when it matches your request.

Disconnect Daasity

To remove the local Codex configuration, run: codex mcp remove daasity. You can also revoke the connection from Daasity under Connect Your AI.

Troubleshooting by symptom

What you see	What to do
command not found: codex	Install Codex CLI with npm install -g @openai/codex, then open a new Terminal window.
MCP tool call requires approval, but approval policy is never	Use the interactive step-6 command with --ask-for-approval on-request. Do not use codex exec for the first test.
Codex asks whether you trust a directory	Select No, quit for folders you do not recognize. Use the dedicated empty ~/daasity-mcp-test folder instead.
The Daasity sign-in page opens	Expected behavior. Confirm the correct workspace and read-only permissions before approving.

Final readiness check

Run through these before relying on the connection:

Codex CLI: installed, confirmed with codex --version MCP server: added with your own URL copied from Connect Your AI Authorization: codex mcp login daasity returned success Test: find_views returned view names from ~/daasity-mcp-test