stack_pains — Buyer Signals MCP Tool
stack_pains
(stack pains) is one of 6 tools on the
Buyer Signals
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call stack_pains from your client
- Claude Code Buyer Signals stack_pains run in your project directory
- Claude Desktop Buyer Signals stack_pains ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Buyer Signals stack_pains ~/.cursor/mcp.json
- VS Code Buyer Signals stack_pains .vscode/mcp.json
- Zed Buyer Signals stack_pains ~/.config/zed/settings.json
- Windsurf Buyer Signals stack_pains ~/.codeium/windsurf/mcp_config.json
- Cline Buyer Signals stack_pains ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Buyer Signals stack_pains ~/.gemini/settings.json
- Grok Buyer Signals stack_pains .mcp.json (in your project root)
- ChatGPT Buyer Signals stack_pains Settings → Connectors → Advanced → Developer mode
- Claude.ai Buyer Signals stack_pains Settings → Connectors → Add custom connector
- LangChain Buyer Signals stack_pains pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http buyersignals https://signals.openkrill.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 October 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.