Craft MCP
for LuumenAI

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.

The Craft MCP toolbox

3 tools: 1 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadCraft readRead/search Craft; batch with semicolons.
  • WriteBlocks revertReverts a previous mutation if blocks haven't been modified since. Approval by default
  • WriteCraft writeWrite; batch semicolons. Approval by default

One prompt, start to finish

What a governed Craft MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to Craft MCP?

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.

Can LuumenAI change things in Craft MCP on its own?

Read actions answer immediately. Anything that writes — blocks revert, craft write — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

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.

Is there an audit trail?

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.

Put Craft MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.