QUIQQER + AI AGENTS
Connect AI agents to QUIQQER and let them work with content, media, users and modular business applications—with controlled permissions.
BEYOND THE PROMPT BOX
AI in a CMS should not stop at generating text. QUIQQER gives agents structured, permission-controlled access to the platform around the content.
TYPICAL CMS AI
A prompt creates text, but the surrounding content model, workflows and business data remain disconnected.
Prompt Text Manual work
QUIQQER AGENT
An authenticated agent can discover available tools, work with structured resources and leave changes in a reviewable state.
Intent Permitted tools Verified result
REAL WORK, NOT A GIMMICK
Give each agent a clear task and only the capabilities it needs. These examples use operations available in the reviewed QUIQQER codebase.
Find active German pages without an English language link. Create linked English copies as inactive drafts for review.
Find pages with missing SEO titles or descriptions and prepare metadata updates without publishing unrelated changes.
Prepare temporary invoices or work with contracts and memberships when the corresponding packages and permissions are available.
Discover package capabilities, load QUIQQER skills and follow extension-specific workflows while working on the codebase.
CAPABILITIES
QUIQQER packages publish purpose-built tools. What an agent sees depends on the installed packages, its authenticated user and the permissions granted to that user.
| Platform area | Read | Create | Update | Execute |
|---|---|---|---|---|
| Pages & content | ✓ | ✓ | ✓ | ✓ |
| Bricks & layouts | ✓ | ✓ | ✓ | — |
| Media | ✓ | ✓ | ✓ | ✓ |
| Users & groups | ✓ | ✓ | ✓ | ✓ |
| Tags & menus | ✓ | ✓ | ✓ | — |
| Translations & feeds | ✓ | ✓ | ✓ | ✓ |
| Contracts & invoices | ✓ | ✓ | ✓ | ✓ |
Execute means a defined operation such as activate, publish, refresh, invite, post or cancel—not unrestricted code execution. Every call still passes the relevant QUIQQER permission checks.
PERMISSION-CONTROLLED BY DESIGN
An AI connection does not bypass QUIQQER. The authenticated MCP session represents a concrete QUIQQER user, and packages publish only the tools available to that user.
Use OAuth or a personal access token tied to a specific QUIQQER user instead of sharing an administrator account.
Permission changes affect the published tool registry without requiring a new OAuth authorization.
Invalid or expired authenticated requests are rejected. They never fall back to anonymous target-system access.
BUILT ON AN OPEN PROTOCOL
Start with discovery. Authenticate only when the agent needs to work on a real system. QUIQQER keeps public knowledge and target-system actions deliberately separate.
https://www.quiqqer.com/mcp
https://your-quiqqer.example/mcp
WORKS WITH MCP-COMPATIBLE AI CLIENTS
Connect an AI client that supports MCP over Streamable HTTP. The available capabilities come from QUIQQER and its installed packages—not from a proprietary prompt layer.
EXAMPLE WORKFLOW
“Find active German pages without an English language link. Create linked English copies as inactive drafts and report what changed.”
Read the relevant German pages and their language links.
Find active pages without a connected English version.
Prepare English copies as inactive drafts—never silently publish them.
Link the German and English language variants.
Summarize every change for review and approval.
Illustrative workflow. Exact results depend on the project state, installed packages and granted permissions.