Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@vailent/pulse-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@vailent/pulse-mcp

Pulse MCP server for Claude Code. Manage pods, features, workstreams, bugs, and more — all from your terminal.

Quick Setup (2 minutes)

1. Create an npm account (skip if you have one)

npm adduser

Follow the prompts to create your account at npmjs.com.

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

npm login --scope=@vailent

4. Add to Claude Code

Run this once from any directory:

claude mcp add pulse-dev -- npx -y @vailent/pulse-mcp

5. Verify it works

Open Claude Code and ask:

what pods exist?

You should see a list of active pods. That's it — you're connected.

What You Can Do

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
"Give me my daily briefing"	AI-generated focus items for today
"What happened this 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

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

Troubleshooting

"Tool not found" or MCP not connecting

Make sure the server is registered:

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:

export PULSE_SUPABASE_URL=https://eppugcfjlqovlauykzfe.supabase.co
export PULSE_SUPABASE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImVwcHVnY2ZqbHFvdmxhdXlremZlIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NzQwNTg2NTYsImV4cCI6MjA4OTYzNDY1Nn0.x9u7sSKnSlTFRWCu--D8zt81IuOmoXXHG3fb3kcRvBc

Need to update to the latest version

npx -y @vailent/pulse-mcp@latest

Or clear the npx cache:

npx clear-npx-cache && claude mcp remove pulse-dev && claude mcp add 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:

export PULSE_SUPABASE_URL=https://your-project.supabase.co
export PULSE_SUPABASE_KEY=your-anon-key