Claude & MCP — later on
MCP connects Claude (Chat) with the Cockpit: search centers, create news, submit drafts, sometimes approve.
This is not the same as v0. v0 = Website design. Claude + MCP = Content and data in the Cockpit via voice.
Also not via MCP: Social media (posts, approvals, engage, performance), Content Planner, and Dispatch — use the dashboard for those. Full scope: Claude & MCP → v0, Claude/MCP and Cockpit.
When is it worthwhile?
| Situation | MCP yes/no |
|---|---|
| You quickly manage many news/events/offers via chat | Yes — after 1–2 weeks of Cockpit basics |
| You are creating first website in v0 | No — first Website with v0 (short path) |
| You want to edit social posts or comments | No — Social media — getting started |
| You need the Content Planner (calendar) | No — /dashboard/content/planner in the browser |
| IT has not sent you MCP-URL | Wait — nothing works without URL |
Start in 3 steps (when IT is ready)
- Connect Claude & Cockpit — Way A (Remote) = 3 clicks, no installation (Claude Pro/Team).
- Test in chat: “Which centers do I know?” or “List shops in center [Slug].”
- Note: New content lands as draft under Workflow & Approvals — not live immediately.
How to test
- Claude correctly names center names and IDs.
- A test draft appears in the Cockpit under Workflow (after “create a test news … for approval”).
Next page
Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/content-creator-handbuch/onboarding-claude-mcp-spaeter