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.

Setup

1. npm access (one-time)

Create an npm account if you don't have one:

npm adduser

Ask Sal to invite you to the Vailent npm org. Accept the email invite, then log in:

npm login --scope=@vailent

2. Install Pulse MCP

npx -p @vailent/pulse-mcp pulse-setup

Restart Claude Code. You're connected.

Verify it works

Open Claude Code in any project and ask:

what pods exist?

You should see a list of active pods. That's it.

What You Can Do

Talk to Claude naturally — the MCP tools handle the rest.

Ask Claude...	What happens
"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 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

All Tools

Tool	Description
`pulse_pods`	List, get, create, update pods
`pulse_pod_members`	Manage pod membership (add, remove, update roles)
`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

MCP not connecting

Check that it's registered:

claude mcp list

You should see pulse-dev with status Connected. If not, re-run setup:

npx -p @vailent/pulse-mcp pulse-setup

Need to update to the latest version

npx clear-npx-cache
npx -p @vailent/pulse-mcp pulse-setup

Then restart Claude Code.

Manual setup (if pulse-setup doesn't work)

claude mcp add --scope user --transport stdio pulse-dev -- npx -y @vailent/pulse-mcp

Then add the service role key to ~/.claude.json under the pulse-dev server's env:

"env": {
  "PULSE_SUPABASE_KEY": "ask Sal for the key"
}