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