Jetzt neu und frisch, besser vom Niederrhein. 
KLXM Studio – Home
Get in touch

Running a website · Advanced · 0:57 min

API tokens & “Submitted” (approval)

Create tokens for AI assistants (MCP) and the REST API – changes only after approval.

No sound, with subtitles German and English subtitles – switch them on and off with “CC” in the player. The video is hosted on this server and only loads when you press play. The steps below are the full text of the video.

Goal

An AI assistant may make suggestions, but a person decides: you review every change under “Submitted”.

Prerequisites

  • Permissions “API & MCP” and “review submitted changes”.

Step by step

Transcript: every step matches one subtitle in the video.

  1. API & MCP: access for automations and AI assistants such as Claude.
  2. “Änderungen: Zur Freigabe” (for approval) – a person checks every change before it goes live.
  3. The token is shown only once – copy it to your password manager right away (blurred here).
  4. When the assistant now changes something, it lands in KLXM Ai › Eingereicht (submitted).
  5. Check the origin (token, channel) and before/after – then “Übernehmen” (apply) or “Ablehnen” (reject).
  6. 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 mycms https://www.ihre-website.de/mcp \
  --header "Authorization: Bearer cms_IHR_TOKEN"

Tips & pitfalls

Tip

“Read only” is enough for reports and checks.

Tip

Optional: “valid until” limits a token in time.

Watch out

Never put tokens in emails, tickets or code repositories – treat them like passwords.

Watch out

Existing tokens stay on “apply directly” until you switch them.