DeepWiki MCP
for LuumenAI

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.

The DeepWiki MCP toolbox

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

  • WriteAsk questionAsk any question about a GitHub repository and get an AI-powered, context-grounded response. Approval by default
  • WriteRead wiki contentsView documentation about a GitHub repository. Approval by default
  • WriteRead wiki structureGet a list of documentation topics for a GitHub repository. Approval by default

Questions

How does LuumenAI connect to DeepWiki MCP?

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.

Can LuumenAI change things in DeepWiki MCP on its own?

Read actions answer immediately. Anything that writes — ask question, read wiki contents, read wiki structure — is shown as a plan and requires approval by default. 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 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.

Put DeepWiki MCP to work with Luumen

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