style_answer — Capucine MCP Prompt

style_answer 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 style_answer from your client

• Claude Code Capucine Prompt/style_answer run in your project directory
• Claude Desktop Capucine Prompt/style_answer ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Capucine Prompt/style_answer ~/.cursor/mcp.json
• VS Code Capucine Prompt/style_answer .vscode/mcp.json
• Zed Capucine Prompt/style_answer ~/.config/zed/settings.json
• Windsurf Capucine Prompt/style_answer ~/.codeium/windsurf/mcp_config.json
• Cline Capucine Prompt/style_answer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Capucine Prompt/style_answer ~/.gemini/settings.json
• Grok Capucine Prompt/style_answer .mcp.json (in your project root)
• ChatGPT Capucine Prompt/style_answer Settings → Connectors → Advanced → Developer mode
• Claude.ai Capucine Prompt/style_answer Settings → Connectors → Add custom connector
• LangChain Capucine Prompt/style_answer pip install langchain-mcp-adapters

Other prompts on this server

• geo_grounded_answer
• shop_a_piece
• rodez_dinner_look
• leather_office_look
• weather_gps_look
• wear_check_piece

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.