Manage with ChatGPT, Claude or Gemini
Sosta has an open MCP server (Model Context Protocol). Connect your favorite AI assistant and maintain your website + shifts in natural language.
- "Write me 3 suggestions for a warm About block, my house has been running since 1998."
- "What shifts do I have today? Who confirmed?"
- "Confirm all proposed shifts for next Saturday."
- "Change my opening hours on Friday to 14:00 to 02:00."
Prerequisites
- Sosta account (the free editor is enough — going live is optional)
- One of the supported AI assistants: ChatGPT Plus/Team, Claude Desktop, Gemini, or another MCP-capable client
Step 1: Create an API key in Sosta
Open the connectors page
In the Manager UI on the left click "AI connectors". If you open the page for the first time it is empty — click "Create first connector".
Name + profile
Give the connector a meaningful name (e.g. "ChatGPT Sandra", "Claude Desktop private").
Pick a permission profile:
- Read-only: only read, change nothing. Good for testing.
- Site editor: change blocks, but no go-live publish.
- Site full (recommended): everything incl. go-live publish + custom domain.
- Shift manager: only manage shift bookings.
- Full access: all tools. Only for highly trusted AI assistants.
Validity + create
Recommended validity: 1 year. You can revoke the key manually at any time.
Click "Create connector". The key is shown once — copy it safely! It is not shown again.
Treat the key like a password. If it falls into the wrong hands, someone can edit your site. In an emergency, revoke and create a new one.
Step 2: Connect your AI assistant
Claude Desktop
Anthropic's official desktop client (macOS + Windows).
- Open the config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Insert the Sosta entry:
{ "mcpServers": { "sosta": { "url": "https://mcp.sosta.app", "headers": { "Authorization": "Bearer sk_sosta_live_DEIN_KEY_HIER" } } } }jsonIf other MCP servers are already configured: insert the
sostaobject additionally, do not overwrite the whole file. - Restart Claude Desktop
- In a new conversation: the Sosta tool icon appears. Test: "What shifts do I have today?"
ChatGPT (custom GPT)
Requires ChatGPT Plus or Team with connectors feature.
- In ChatGPT → "Explore GPTs" → "Create"
- Tab "Configure" → at the bottom "Add Action"
- Insert MCP endpoint:
https://mcp.sosta.app
text - Auth type:
Bearer Token→ insert token - Save the GPT. In a test conversation: "What shifts do I have today?"
Other AI assistants
Gemini Extensions, Mistral, local Llama setups with an MCP bridge.
Every MCP-capable client can be connected:
- Endpoint:
https://mcp.sosta.app - Transport: HTTP + (optional SSE)
- Auth:
Authorization: Bearer sk_sosta_live_… - Protocol: Model Context Protocol 2024-11-05
Tips for good prompts
Examples that work well in practice:
Concrete workflows
Roster maintenance via chat
- "Who is in the roster today, sorted by stage name?" — AI calls search_setcards/list
- "Find me all setcards with 'Mia' in the name." — search_setcards with query='mia'
- "Who is present today?" — list with presentOnly=true
Roster mutations run through the Manager UI (GDPR Art. 9 — image upload + consent).
Adjust hosted-site content
- "List my site blocks." — list_blocks
- "Change the HERO headline to 'Spring offers until end of April'." — update_block
- "Insert an ABOUT block with the following text: …" — add_block
- "Publish my site." — request_publish (checks readiness)
update_block checks block-type validation. For invalid fields the AI gets clear error hints back.
Shift workflow
- "What open requests do I have for next week?" — list_shifts
- "Propose a shift: Mia, Friday 18:00-02:00." — propose_shift
- "Confirm shift XYZ." — confirm_shift
- "Cancel shift ABC, reason: called in sick at short notice." — cancel_shift
Shift mutations are irreversible via audit. The worker sees all changes in the Talents PWA.
Audit + security
Every command the AI runs lands in the connector audit. You see exactly who-did-what-when — even if a connector was compromised.
- Open connector audit log — filter by connector, action, time window
- Audit entries are retained for 90 days (GDPR obligation)
- On suspicion: revoke connector immediately (connector list)
When something does not work
"AI says: Authentication failed"
Check the bearer token format. Must start with sk_sosta_live_. The token may have been revoked — create a new one in /connectors.
"AI replies: invalid_content_for_HERO"
The AI sent invalid block fields. Check the tool response issues for exact paths. update_block + add_block validate strictly against the renderer schema.
"AI says: rate limit exceeded"
Per connector 60 requests/min. For bulk actions ask the AI to pause ('do this in batches of 5 with a 10 s pause').
"Tool is not offered at all"
Check permission profile — a read-only connector does not see any update_* tools. In /connectors → edit pencil → set a new profile.