faq.md — Côte Privée: private driver in Burgundy MCP Resource
faq.md
is one of 3 resources on the
Côte Privée: private driver in Burgundy
MCP server. Connect the server and your client can attach it as context.
by client
How to attach faq.md from your client
- Claude Code Côte Privée: private driver in Burgundy Resource/faq.md run in your project directory
- Claude Desktop Côte Privée: private driver in Burgundy Resource/faq.md ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Côte Privée: private driver in Burgundy Resource/faq.md ~/.cursor/mcp.json
- VS Code Côte Privée: private driver in Burgundy Resource/faq.md .vscode/mcp.json
- Zed Côte Privée: private driver in Burgundy Resource/faq.md ~/.config/zed/settings.json
- Windsurf Côte Privée: private driver in Burgundy Resource/faq.md ~/.codeium/windsurf/mcp_config.json
- Cline Côte Privée: private driver in Burgundy Resource/faq.md ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Côte Privée: private driver in Burgundy Resource/faq.md ~/.gemini/settings.json
- Grok Côte Privée: private driver in Burgundy Resource/faq.md .mcp.json (in your project root)
- ChatGPT Côte Privée: private driver in Burgundy Resource/faq.md Settings → Connectors → Advanced → Developer mode
- Claude.ai Côte Privée: private driver in Burgundy Resource/faq.md Settings → Connectors → Add custom connector
- LangChain Côte Privée: private driver in Burgundy Resource/faq.md pip install langchain-mcp-adapters
Other resources on this server
Côte Privée: private driver in Burgundy also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 27 October 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.