Ask Devin about any repository, including the private ones
Put questions about a codebase to Devin from the terminal and get answers grounded in the actual repository, private ones included. You can also manage automations, knowledge notes, code scans, and billing tags, and list what Devin is connected to. Every Devin MCP tool is a write tool, so each call is previewed and approved before it runs by default. Luumen connects with an API key.
22 tools: 0 read, 22 write. Reads answer instantly. Writes require approval by default. Everything is logged.
Authorize once with API token. 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 ask question, devin automation manage, devin billing tag manage, devin blueprint test, and more. 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 Devin 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.