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