Open your ChatData workspace.

Sign in once, then ChatData opens the AI-native data catalog for your company domain. Claude Code and Codex connection steps live inside the workspace.

Workspace sign in

Workspace connected.

Trial Checking

Loading workspace status.

Metadata sync

Workspace Connected

Token is domain scoped.

Evidence target 2h/week

Start by reclaiming one small analyst loop.

Estimated value $1K/mo

At roughly $120/hour and 2 hours/week.

Record it /chatdata:proof

Make saved time visible before the trial ends.

Claude Code starter kit

Verify setup, run one trusted workflow, sync reusable context when approved, then record proof before the trial ends.

Status command

/chatdata:status

Audit command

/chatdata:audit-context

Sync command

/chatdata:sync-context

Evidence receipt command

/chatdata:proof --record --workflow "first trusted answer" --question "What did ChatData make safer or faster?" --confidence "medium" --time-saved-minutes "30"

Connect Claude or Codex

Install or update the ChatData Claude plugin first. The plugin provides the /chatdata: commands and enforces MCP-backed sync after useful analysis. Add plugin marketplace claude plugin marketplace add https://github.com/getchatdata/chatdata-claude-marketplace.git Install plugin claude plugin install chatdata@chatdata Already installed update claude plugin update chatdata@chatdata Verify plugin claude plugin list
Click Copy terminal setup command, paste it into Terminal, and press Return. This writes the config JSON to ~/.chatdata/config.json. Do not paste the JSON separately. If Terminal says zsh: command not found: token:, you copied the raw JSON instead of the terminal setup command. Save config command
Build the local MCP package once: Build command cd /Users/parasdoshi/Documents/ChatData/packages/mcp && npm install && npm run build
Add ChatData to Claude Code or Codex: Claude Code command claude mcp add --scope user chatdata -- node /Users/parasdoshi/Documents/ChatData/packages/mcp/dist/index.js If Terminal says MCP server chatdata already exists in user config, ChatData is already registered. Run this and continue if it shows Status: Connected and the ChatData packages/mcp/dist/index.js path: Already connected check claude mcp get chatdata Only reset the Claude entry if that check points to an old or wrong path: Reset wrong Claude entry claude mcp remove chatdata -s user && claude mcp add --scope user chatdata -- node /Users/parasdoshi/Documents/ChatData/packages/mcp/dist/index.js Codex command codex mcp add chatdata -- node /Users/parasdoshi/Documents/ChatData/packages/mcp/dist/index.js
Verify the server is connected, then restart Claude Code or Codex: Verify command claude mcp list
In a new Claude Code or Codex chat, paste this exact request. Do not type only chatdata_doctor; if a planning screen opens, press Esc and use this sentence instead. Doctor request Use the ChatData MCP server and run the chatdata_doctor tool. Show me the JSON result.

Advanced access token Client config

Opening ChatData.

Open your ChatData workspace.

Workspace sign in

Claude Code starter kit

Connect Claude or Codex