Read and update Craft docs, daily notes, and tasks from the terminal
Connect Craft and Luumen can read the documents your team already keeps — runbooks, incident notes, daily notes, task lists, collections. Ask what a runbook says and get the answer right away. When something needs to change, Luumen drafts the edit, shows it to you, and waits for your approval before writing it back. Access is set up with OAuth dynamic client registration.
3 tools: 1 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Craft 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.
This connection exposes write actions such as blocks revert, craft write. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Craft 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.