chsm04/pulse
Local Channel plugin for Claude Code — push notifications into sessions via HTTP. No Discord, no Slack, just curl.
Platform-specific configuration:
{
"mcpServers": {
"pulse": {
"command": "npx",
"args": [
"-y",
"pulse"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
A local Channel plugin that injects external notifications into Claude Code sessions in real-time.
No Discord, no Telegram — just a single HTTP POST to push messages into your conversation.
[한국어](./README.ko.md)
Claude Code's Channels require external messaging services like Discord or Slack to push messages into a session. This creates unnecessary friction — you need a bot token, an account, network access to a third-party service, all just to send a simple notification from a local script.
Pulse is an event abstraction layer that removes this dependency. Any local process that can make an HTTP call can now communicate with your Claude Code session directly, without routing through an external messenger.
Hooks / Scripts / Cron
↓ HTTP POST localhost:3400/notify
Pulse MCP Server
↓ notifications/claude/channel
Real-time injection into Claude Code sessionPulse leverages Claude Code's Channels protocol. The MCP server registers with the claude/channel capability and forwards HTTP requests to the session via notifications/claude/channel.
/plugins → Add Marketplace → enter chsm04/pulse
Select pulse from the marketplace list → Install
claude --dangerously-load-development-channels plugin:pulse@pulse/notifyDeliver a notification to the Claude Code session.
curl -s -X POST localhost:3400/notify \
-H "Content-Type: application/json" \
-d '{"text":"Build failed!","source":"ci","level":"error"}'| Field | Type | Required | Description | |-------|------|----------|-------------| | text | string | Yes | Notification content | | source | string | No | Origin identifier (ci, deploy, cron, etc.) | | level | string | No | info \| warn \| error (default: inf
Loading reviews...