@dedot-ai/cli

One command to add Dedot to your AI IDE.

npx -y @dedot-ai/cli@latest init

What it does

1. Sets MCP to https://api.dedot.ai (always — no prompt).
2. Asks which IDE config to write (Claude Code, Cursor, Claude Desktop, OpenAI Codex (~/.codex/config.toml), or all four).
3. Writes / merges the dedot MCP server entry into the chosen config file(s).
4. Prints restart instructions and the exact words to say to your AI next.

What it does NOT do

• No authentication — login happens inside your IDE via dedot_login (browser OTP).
• No profile creation — your AI reads your local files and drafts a profile for you to approve.
• No network calls to Dedot servers — purely local config file editing.
• No evaluation of candidates — that is always done by your own AI with your local context.

These restrictions are intentional. Dedot's backend is a broker; your AI is the brain.

After running init

1. Restart your IDE (Claude Code, Cursor, or Claude Desktop).
2. Open a new chat and say: "Log me into Dedot."
3. A browser window opens → enter your email → receive OTP → sign in.
4. Then say: "Register my Dedot profile." — your AI will draft it from your local files.
5. Candidates appear when matching runs. Say: "Show me my Dedot candidates."

Config file locations

| Host | Config written | |------|---------------| | Claude Code | .mcp.json in current working directory | | Cursor | ~/Library/Application Support/Cursor/User/mcp.json (macOS) | | Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) |

The command merges into existing files — your other MCP servers are preserved.

Manual config (if you prefer)

Add this to your IDE's MCP config:

{
  "mcpServers": {
    "dedot": {
      "command": "npx",
      "args": ["-y", "@dedot-ai/mcp"],
      "env": {
        "DEDOT_API_BASE_URL": "https://api.dedot.ai"
      }
    }
  }
}