Read design files and history, then publish the artifact once you approve it
Connect Magic Patterns and Luumen can look at a design the way you would: current status, the active artifact, the files inside it, and the version history behind it. When a change is needed — editing artifact files, publishing a new active artifact, starting a new design — Luumen shows the plan first and waits for your approval before it writes. Access uses OAuth with dynamic client registration.
23 tools: 10 read, 13 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Magic Patterns MCP run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create design, create design system, create inspiration document, create new artifact, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Magic Patterns MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.