Read and update your team's Eraser diagrams and docs from the terminal
Connect Eraser and Luumen can read the architecture your team already keeps there. It lists files, opens a document's markdown, and pulls a diagram's DSL for context during an incident or a review. When something is out of date, it drafts the new diagram or document and holds the change for your approval first. Sign in once with OAuth.
42 tools: 16 read, 26 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Eraser 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 — add or remove template or reference, create diagram, create document, create file, and more — is shown as a plan and requires approval by default, including the 14 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 Eraser 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.