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>
1.0 KiB
1.0 KiB
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.
- Open Claude Desktop → Settings → Developer → Edit Config. This opens
%APPDATA%\Claude\claude_desktop_config.json. - Merge in the
mcpServersblock fromclaude_desktop_config.example.json. Keep any servers you already have. - Restart Claude Desktop. The tools icon should list
social-managerandodoo-mcp.
No secrets go in this file.
social-managerreads the Meta token from this project's.env.odoo-mcpreads its Odoo login fromD:\MCS_Repos\2026\ODOO-MCP\.env. It's read-only unlessODOO_READ_ONLY=falseis 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.