who_works_on — CKB Pulse MCP Tool
who_works_on
(who works on) is one of 8 tools on the
CKB Pulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call who_works_on from your client
- Claude Code CKB Pulse who_works_on run in your project directory
- Claude Desktop CKB Pulse who_works_on ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CKB Pulse who_works_on ~/.cursor/mcp.json
- VS Code CKB Pulse who_works_on .vscode/mcp.json
- Zed CKB Pulse who_works_on ~/.config/zed/settings.json
- Windsurf CKB Pulse who_works_on ~/.codeium/windsurf/mcp_config.json
- Cline CKB Pulse who_works_on ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CKB Pulse who_works_on ~/.gemini/settings.json
- Grok CKB Pulse who_works_on .mcp.json (in your project root)
- ChatGPT CKB Pulse who_works_on Settings → Connectors → Advanced → Developer mode
- Claude.ai CKB Pulse who_works_on Settings → Connectors → Add custom connector
- LangChain CKB Pulse who_works_on pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ckb-pulse https://pulse-lab.lusocryptolabs.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.