c309581df0
Dashboard (content library, publishing queue with approvals, inbox, team management, AI runs), Meta connector, branded PDF reports, agent skills, and Docker packaging (Dockerfile, docker-compose with Caddy HTTPS, backup and path-relocation scripts). Client data, live data and secrets are excluded via .gitignore. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14 lines
1.0 KiB
Markdown
14 lines
1.0 KiB
Markdown
# Connecting Claude Desktop
|
|
|
|
Claude Desktop can use the same two connectors as Claude Code and the dashboard. Then you can ask things like "how did Maison de Treats do this week?" or "what's overdue for the design team?" in plain chat.
|
|
|
|
1. Open Claude Desktop → **Settings → Developer → Edit Config**. This opens `%APPDATA%\Claude\claude_desktop_config.json`.
|
|
2. Merge in the `mcpServers` block from [`claude_desktop_config.example.json`](claude_desktop_config.example.json). Keep any servers you already have.
|
|
3. Restart Claude Desktop. The tools icon should list `social-manager` and `odoo-mcp`.
|
|
|
|
**No secrets go in this file.**
|
|
- `social-manager` reads the Meta token from this project's `.env`.
|
|
- `odoo-mcp` reads its Odoo login from `D:\MCS_Repos\2026\ODOO-MCP\.env`. It's read-only unless `ODOO_READ_ONLY=false` is set there, and every write asks for confirmation.
|
|
|
|
For the skills (audits, weekly plans), charts and branded PDFs, use Claude Code in this folder or the dashboard. Claude Desktop doesn't load project skills.
|