wear_check_piece — Capucine MCP Prompt
wear_check_piece
is one of 7 prompts on the
Capucine
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke wear_check_piece from your client
- Claude Code Capucine Prompt/wear_check_piece run in your project directory
- Claude Desktop Capucine Prompt/wear_check_piece ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Capucine Prompt/wear_check_piece ~/.cursor/mcp.json
- VS Code Capucine Prompt/wear_check_piece .vscode/mcp.json
- Zed Capucine Prompt/wear_check_piece ~/.config/zed/settings.json
- Windsurf Capucine Prompt/wear_check_piece ~/.codeium/windsurf/mcp_config.json
- Cline Capucine Prompt/wear_check_piece ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Capucine Prompt/wear_check_piece ~/.gemini/settings.json
- Grok Capucine Prompt/wear_check_piece .mcp.json (in your project root)
- ChatGPT Capucine Prompt/wear_check_piece Settings → Connectors → Advanced → Developer mode
- Claude.ai Capucine Prompt/wear_check_piece Settings → Connectors → Add custom connector
- LangChain Capucine Prompt/wear_check_piece pip install langchain-mcp-adapters
Other prompts on this server
Capucine also offers 7 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.