public_style_api — Capucine MCP Resource

public_style_api is one of 7 resources on the Capucine MCP server. Connect the server and your client can attach it as context.

by client

How to attach public_style_api from your client

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

Other resources on this server

• capucine_look_widget
• capucine_weather_board_widget
• capucine_shop_widget
• citation_rules
• piece_hubs_resource
• llms_txt_resource

Capucine also offers 7 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.