Skip to main content
Guide · How-to

Wire up Claude Code

Senkani's MCP server registers globally with Claude Code via senkani init. No config files to maintain.

What senkani init modifies

  1. Writes ~/.senkani/bin/senkani-hook (the compiled Mach-O hook binary, zero deps, < 5 ms startup).
  2. Appends an entry to ~/.claude/settings.json under mcpServers: 
    "mcpServers": {{
  "senkani": {{
    "command": "/Users/you/.senkani/bin/senkani",
    "args": []
  }}
}}
  3. Appends PreToolUse + PostToolUse hook entries with matcher Read|Bash|Grep|Write|Edit.
  4. Does not touch any other settings. Does not require sudo. Does not modify shell profiles.

Verify

senkani doctor

Should show "MCP server registered" and "Hooks registered." If not, run senkani doctor --fix.

First session

  1. Launch the senkani app (senkani with no args, or open SenkaniApp).
  2. Open a Terminal pane (⌘K → "Terminal").
  3. Run claude inside the pane. The MCP server starts; the agent sees all 19 senkani tools on top of Claude Code's built-ins.
  4. Open an Analytics pane side-by-side (⌘K → "Analytics"). Watch token savings accumulate as the session runs.
⚐
MCP activation is gated on SENKANI_PANE_ID, which the app injects only into managed panes. Run claude in a non-Senkani terminal and it won't see the senkani tools — by design.

Next

Your first session →