@cclarity-packages/cli

Init-only — adds the CClarity MCP plugin to your IDE.

The stdio server lives in a separate package: @cclarity-packages/mcp.

npx -y @cclarity-packages/cli@latest init

Then say "Login me into CClarity". The IDE runs npx -y @cclarity-packages/mcp cclarity-mcp, which opens the browser and proxies tools.

How it works

npx -y @cclarity-packages/cli@latest init
  └─▶ Writes .mcp.json (etc.) with: npx -y @cclarity-packages/mcp cclarity-mcp
  └─▶ Restart IDE → "Login me into CClarity"
        └─▶ @cclarity-packages/mcp: browser + callback + tools

| Package | Role | |--------|------| | @cclarity-packages/cli | init only (this package) | | @cclarity-packages/mcp | Stdio MCP, cclarity_login, upstream proxy — README |

What your AI can do after login

"Login me into CClarity"
"List my lead profiles"
"Who engaged with my latest LinkedIn posts?"

Hosted “CClarity” in Claude vs local MCP

If login only returns a URL in JSON, you are on a cloud connector, not npx @cclarity-packages/mcp. Use init (or manual JSON below) so the project runs the mcp package.

After init, the tool list should include cclarity_login.

Manual config (same as init output)

Claude Code — project .mcp.json:

{
  "mcpServers": {
    "cclarity": {
      "command": "npx",
      "args": ["-y", "@cclarity-packages/mcp", "cclarity-mcp"],
      "env": { "CCLARITY_MCP_URL": "https://apistaging.cclarity.io" }
    }
  }
}

Environment (inherited by the MCP process)

| Variable | Purpose | |----------|---------| | CCLARITY_MCP_URL | API base (written by init) | | CCLARITY_CONFIG_DIR | Credentials dir (used by mcp package) |

Full troubleshooting: ../mcp/README.md.

Development (this repo)

cd packages/cli
npm install
npm run build