Running a website · Advanced · 0:58 min
API tokens & “Submitted” (approval)
Create tokens for AI assistantProgram that uses artificial intelligence to handle tasks in natural language – such as suggesting texts, translating or answering questions. Results should always be reviewed by people. (MCPModel Context Protocol: open standard through which AI assistants access tools and data. Via an MCP server, such assistants can, for example, read a website’s content or create drafts.modelcontextprotocol.io (opens in a new tab)) and the REST APIWidely used form of programming interface over HTTP: content is retrieved, created or changed via addresses, usually in JSON format.en.wikipedia.org (opens in a new tab) – changes only after approval.
Goal
An AI assistant may make suggestions, but a person decides: you review every change under “Submitted”.
Prerequisites
- Permissions “APIApplication programming interface: programs use it to exchange data without the user interface – for example to take over entries from another system.en.wikipedia.org (opens in a new tab) & MCP” and “review submitted changes”.
Step by step
Transcript: every step matches one subtitle in the video.
- System › Einstellungen der Funktionen (feature settings) › API & MCP: access for automations and AI assistants such as Claude.
- “Änderungen: Zur Freigabe” (for approval) – a person checks every change before it goes live.
- The token is shown only once – copy it to your password manager right away (blurred here).
- When the assistant now changes something, it lands in KLXM AI › Eingereicht (submitted).
- Check the origin (token, channel) and before/after – then “Übernehmen” (apply) or “Ablehnen” (reject).
- Every submission stays logged. Tokens can be switched or revoked at any time.
Commands & configuration
# MCP-Server in Claude Code verbinden (Token aus dem Passwortmanager)
claude mcp add --transport http klxm-studio https://www.ihre-website.de/mcp \
--header "Authorization: Bearer cms_IHR_TOKEN"
Tips & pitfalls
“Read only” is enough for reports and checks.
Optional: “valid until” limits a token in time.
Never put tokens in emails, tickets or code repositories – treat them like passwords.
Existing tokens stay on “apply directly” until you switch them.