@vailent/pulse-mcp 1.13.0 → 1.14.0

package/README.md

@@ -2,43 +2,37 @@
 
 Pulse MCP server for [Claude Code](https://docs.anthropic.com/en/docs/claude-code). Manage pods, features, workstreams, bugs, and more — all from your terminal.
 
-## Quick Setup (2 minutes)
+## Setup
 
-### 1. Create an npm account (skip if you have one)
+### 1. npm access (one-time)
 
+Create an npm account if you don't have one:
 ```bash
 npm adduser
 ```
 
-Follow the prompts to create your account at [npmjs.com](https://www.npmjs.com/signup).
-
-### 2. Get added to the Vailent npm org
-
-Ask Sal to invite you using your npm username. You'll get an email — accept the invite.
-
-### 3. Log in to the Vailent scope
-
+Ask Sal to invite you to the Vailent npm org. Accept the email invite, then log in:
 ```bash
 npm login --scope=@vailent
 ```
 
-### 4. Add to Claude Code
-
-Run this once from any directory:
+### 2. Install Pulse MCP
 
 ```bash
-claude mcp add pulse-dev -- npx -y @vailent/pulse-mcp
+npx -p @vailent/pulse-mcp pulse-setup
 ```
 
-### 5. Verify it works
+Restart Claude Code. You're connected.
+
+### Verify it works
 
-Open Claude Code and ask:
+Open Claude Code in any project and ask:
 
 ```
 what pods exist?
 ```
 
-You should see a list of active pods. That's it — you're connected.
+You should see a list of active pods. That's it.
 
 ## What You Can Do
 
@@ -46,68 +40,68 @@ Talk to Claude naturally — the MCP tools handle the rest.
 
 | Ask Claude... | What happens |
 |---|---|
-| "What pods exist?" | Lists all active pods with members |
-| "Show me features for this week" | Lists features by pod and week |
-| "Create a feature called Auth Revamp in pod X" | Creates a new feature |
-| "What bugs are open?" | Lists open bugs with priority |
-| "Show me pending suggestions" | Lists AI suggestions needing review |
+| "What features are in progress this week?" | Lists features by pod and week |
+| "Show me open bugs for Catalyst" | Lists open bugs with priority |
+| "Create a bug: login redirect fails on Safari" | Creates a new bug |
+| "Search for anything about deal creation" | Semantic search across all items |
 | "Give me my daily briefing" | AI-generated focus items for today |
-| "What happened this week?" | Searches activity history |
+| "What PRs are open for PULSE-142?" | Shows PR status for a feature |
+| "Triage the open requests for my pod" | Lists requests needing review |
+| "What did the team ship last week?" | Searches activity history |
 | "Show the team roster" | Lists team members and pod assignments |
-| "What feature requests came in?" | Lists feature requests by source |
 
-### All 11 Tools
+### All Tools
 
 | Tool | Description |
 |---|---|
 | `pulse_pods` | List, get, create, update pods |
 | `pulse_pod_members` | Manage pod membership (add, remove, update roles) |
-| `pulse_features` | List, get, create, update features with phase/step tracking |
-| `pulse_workstreams` | Manage workstreams (projects) |
-| `pulse_requests` | View and manage feature requests |
-| `pulse_bugs` | View and manage bug reports |
-| `pulse_suggestions` | Review, approve, reject AI suggestions |
-| `pulse_events` | Query the activity event stream |
-| `pulse_history` | Search across all historical data |
-| `pulse_briefing` | Generate AI daily briefing by role |
-| `pulse_team` | View team members and assignments |
+| `pulse_pod_repos` | Link GitHub repos to pods |
+| `pulse_features` | Manage features with phase/step tracking |
+| `pulse_workstreams` | Manage workstreams (projects), extract features from PRDs |
+| `pulse_milestones` | Manage workstream milestones |
+| `pulse_requests` | Triage feature requests (accept, decline, defer) |
+| `pulse_bugs` | Track bugs (create, update, schedule) |
+| `pulse_suggestions` | Review and approve AI suggestions |
+| `pulse_search` | Semantic similarity search — find duplicates, related items |
+| `pulse_events` | Activity stream, list PRs for a feature |
+| `pulse_history` | Search shipped features, closed requests, resolved bugs |
+| `pulse_briefing` | AI daily briefing adapted to your role |
+| `pulse_team` | View and manage team members |
 
 ## Troubleshooting
 
-### "Tool not found" or MCP not connecting
+### MCP not connecting
 
-Make sure the server is registered:
+Check that it's registered:
 ```bash
 claude mcp list
 ```
 
-You should see `pulse-dev` in the list. If not, re-run step 4.
-
-### "Missing Supabase credentials" error
-
-This shouldn't happen — the dev database is preconfigured. If it does, set these env vars:
-
+You should see `pulse-dev` with status `Connected`. If not, re-run setup:
 ```bash
-export PULSE_SUPABASE_URL=https://eppugcfjlqovlauykzfe.supabase.co
-export PULSE_SUPABASE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImVwcHVnY2ZqbHFvdmxhdXlremZlIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NzQwNTg2NTYsImV4cCI6MjA4OTYzNDY1Nn0.x9u7sSKnSlTFRWCu--D8zt81IuOmoXXHG3fb3kcRvBc
+npx -p @vailent/pulse-mcp pulse-setup
 ```
 
 ### Need to update to the latest version
 
 ```bash
-npx -y @vailent/pulse-mcp@latest
+npx clear-npx-cache
+npx -p @vailent/pulse-mcp pulse-setup
 ```
 
-Or clear the npx cache:
+Then restart Claude Code.
+
+### Manual setup (if pulse-setup doesn't work)
+
 ```bash
-npx clear-npx-cache && claude mcp remove pulse-dev && claude mcp add pulse-dev -- npx -y @vailent/pulse-mcp
+claude mcp add --scope user --transport stdio pulse-dev -- npx -y @vailent/pulse-mcp
 ```
 
-## Advanced: Custom Supabase Instance
-
-To point at a different Supabase project, set these env vars before running Claude Code:
+Then add the service role key to `~/.claude.json` under the `pulse-dev` server's `env`:
 
-```bash
-export PULSE_SUPABASE_URL=https://your-project.supabase.co
-export PULSE_SUPABASE_KEY=your-anon-key
+```json
+"env": {
+  "PULSE_SUPABASE_KEY": "ask Sal for the key"
+}
 ```

package/dist/server.js

@@ -41722,6 +41722,13 @@ function normalizeWorkItemState(updates, current) {
   return result;
 }
 
+// lib/cascade-request-status.ts
+var TERMINAL_STATUSES = ["shipped", "missed", "killed"];
+async function cascadeStatusToRequests(supabase, featureId, newStatus) {
+  if (!TERMINAL_STATUSES.includes(newStatus)) return;
+  await supabase.from("work_items").update({ status: newStatus, updated_at: (/* @__PURE__ */ new Date()).toISOString() }).eq("accepted_feature_id", featureId);
+}
+
 // tools/features.ts
 async function handleFeatures(params) {
   const supabase = getAdminClient();
@@ -41813,6 +41820,9 @@ async function handleFeatures(params) {
       const updates = normalizeWorkItemState(raw, current || void 0);
       const { error: error2 } = await supabase.from("work_items").update(updates).eq("id", featureId);
       if (error2) return err(error2.message);
+      if (updates.status) {
+        await cascadeStatusToRequests(supabase, featureId, updates.status);
+      }
       return ok({ id: featureId, ...updates }, `Updated feature ${featureId}`);
     }
     case "delete": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vailent/pulse-mcp",
-  "version": "1.13.0",
+  "version": "1.14.0",
   "description": "Pulse MCP server — manage pods, features, workstreams, bugs, and more from Claude Code",
   "type": "module",
   "bin": {