@picahq/cli 0.1.0 → 0.3.0

package/README.md

@@ -18,10 +18,54 @@ Requires Node.js 18+.
 pica init
 ```
 
-This prompts for your Pica API key, saves it to `~/.pica/config.json`, and installs the MCP server into your AI agents (Claude Code, Claude Desktop, Cursor, Windsurf).
+This walks you through:
+1. Entering your Pica API key (validates it)
+2. Choosing which AI agents to install the MCP server into
+3. Choosing global vs project-level installation
 
 Get your API key at [app.picaos.com/settings/api-keys](https://app.picaos.com/settings/api-keys).
 
+Config is saved to `~/.pica/config.json`.
+
+### Re-running init
+
+If you already have a config, `pica init` shows your current setup instead of starting over:
+
+```
+ Pica
+
+  Current Setup
+  ──────────────────────────────────────────
+  API Key:  sk_test_...9j-Y
+  Config:   ~/.pica/config.json
+
+  Agent           Global  Project
+  ──────────────  ──────  ───────
+  Claude Code     ● yes   ● yes
+  Claude Desktop  ● yes   -
+  Cursor          ○ no    ○ no
+  Windsurf        -       -
+
+  - = not detected on this machine
+```
+
+Then it offers targeted actions based on what's missing:
+
+- **Update API key** -- validates the new key, then re-installs to every agent that currently has the MCP (preserving global/project scopes)
+- **Install MCP to more agents** -- only shows detected agents missing the MCP
+- **Install MCP for this project** -- creates `.mcp.json` / `.cursor/mcp.json` in cwd for agents that support project scope
+- **Start fresh** -- full setup flow from scratch
+
+Options that don't apply are hidden. If every detected agent already has the MCP globally, "Install MCP to more agents" won't appear.
+
+### Init flags
+
+| Flag | Effect |
+|------|--------|
+| `-y, --yes` | Skip confirmations |
+| `-g, --global` | Install MCP globally (default, available in all projects) |
+| `-p, --project` | Install MCP for this project only (creates config files in cwd) |
+
 ## Usage
 
 ### Connect a platform
@@ -119,6 +163,19 @@ Every command supports `--json` for machine-readable output.
 
 All API calls route through Pica's passthrough proxy (`api.picaos.com/v1/passthrough`), which injects auth credentials, handles rate limiting, and normalizes responses. Your connection keys tell Pica which credentials to use. You never touch raw OAuth tokens.
 
+## MCP installation
+
+`pica init` writes MCP server configs into the following locations:
+
+| Agent | Global config | Project config |
+|-------|--------------|----------------|
+| Claude Code | `~/.claude.json` | `.mcp.json` |
+| Claude Desktop | `~/Library/Application Support/Claude/claude_desktop_config.json` | n/a |
+| Cursor | `~/.cursor/mcp.json` | `.cursor/mcp.json` |
+| Windsurf | `~/.codeium/windsurf/mcp_config.json` | n/a |
+
+Global installs make the MCP available everywhere. Project installs create config files in your current directory that can be committed and shared with your team (each team member needs their own API key).
+
 ## Development
 
 ```bash
@@ -133,7 +190,7 @@ npm run typecheck  # type check without emitting
 src/
   index.ts              # Commander setup and command registration
   commands/
-    init.ts             # pica init (API key + MCP setup)
+    init.ts             # pica init (setup, status display, targeted actions)
     connection.ts       # pica add, pica list
     platforms.ts        # pica platforms
     actions.ts          # pica search, actions knowledge, exec
@@ -142,7 +199,8 @@ src/
     types.ts            # TypeScript interfaces
     actions.ts          # Action ID normalization, path variable helpers
     config.ts           # ~/.pica/config.json read/write
-    agents.ts           # MCP config for Claude, Cursor, Windsurf
+    agents.ts           # Agent detection, MCP config, status reporting
     platforms.ts        # Platform search and fuzzy matching
     browser.ts          # Open browser for OAuth and API key pages
+    table.ts            # Formatted table output
 ```

package/dist/index.d.ts

@@ -0,0 +1 @@
+#!/usr/bin/env node