Ask questions about any public GitHub repo, grounded in its own docs
When an incident points at an upstream dependency, you can read its documentation without leaving the terminal. DeepWiki MCP lists a repository's documentation topics with DEEPWIKI_MCP_READ_WIKI_STRUCTURE, pulls the pages with DEEPWIKI_MCP_READ_WIKI_CONTENTS, and answers specific questions through DEEPWIKI_MCP_ASK_QUESTION. No credential to set up. All three calls are previewed for your approval by default.
3 tools: 0 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
DeepWiki MCP needs no credential of its own, so there is nothing to authorize. Access is still granted per agent, skill, and team inside Luumen, and every call is logged.
This connection exposes write actions such as ask question, read wiki contents, read wiki structure. 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 DeepWiki 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.