> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DeepWiki AI Connector

> Connect Rootly AI to DeepWiki for architecture documentation and grounded answers about public GitHub repositories.

The **DeepWiki** AI connector gives Rootly AI current architecture context for public GitHub repositories. During an investigation, Rootly AI can explore a repository's generated wiki, read relevant documentation, and ask focused questions about the codebase.

DeepWiki is hosted by Cognition and requires no account, API key, or OAuth authorization. Rootly connects to its public, read-only Model Context Protocol (MCP) endpoint.

<Info>
  DeepWiki works with public GitHub repositories only. To use private repositories or Devin platform actions, connect the separate **[Devin AI connector](/ai/connectors/devin)**.
</Info>

## Before You Start

You need:

* The GitHub owner and repository name for each public codebase Rootly AI should investigate.
* Permission in Rootly to manage AI connectors.

No Cognition or Devin account is required. If a repository is private, make it available to Devin and use the Devin connector instead.

***

## Connect DeepWiki

Use these steps to enable DeepWiki for Rootly AI.

<Steps>
  <Step title="Open AI Connectors">
    In Rootly, go to **AI & Agents → Connectors** and find the **DeepWiki** card.
  </Step>

  <Step title="Connect DeepWiki">
    Click **Connect**. There are no credentials or authorization screens to complete.
  </Step>

  <Step title="Confirm the Connection">
    Rootly checks DeepWiki's hosted MCP endpoint and reviewed tool catalog. The card shows **Connected** after validation succeeds.
  </Step>
</Steps>

***

## What Rootly AI Can Read

Rootly exposes all three tools in DeepWiki's public MCP catalog:

| Tool                  | What it does                                                                       |
| --------------------- | ---------------------------------------------------------------------------------- |
| `read_wiki_structure` | Lists the topics and pages in a public repository's generated wiki.                |
| `read_wiki_contents`  | Reads the generated documentation for a public repository.                         |
| `ask_question`        | Asks a free-text question about a public repository and returns a grounded answer. |

Repository names are sent as `owner/repo`, such as `rails/rails`. Rootly pins these three tool names, so a tool that Cognition adds later does not become available until Rootly reviews it.

## Investigation Examples

Ask questions that name the repository and connect the codebase to the incident:

* *"In `rails/rails`, where is connection-pool checkout implemented, and what can exhaust the pool?"*
* *"Show the architecture sections for `kubernetes/kubernetes` that explain request admission."*
* *"How does `redis/redis` persist data during a restart, and which configuration changes affect recovery time?"*
* *"This stack trace points into an open-source dependency. Find the relevant component and explain the likely failure path."*
* *"Compare the documented retry behavior with the timeout pattern in this incident. What edge cases should we test?"*

For an unfamiliar repository, Rootly AI can inspect the wiki structure before reading a page or asking a detailed question. This helps avoid assumptions about topic names and repository layout.

***

## Access and Data Handling

* **Public repositories only:** DeepWiki cannot read private GitHub repositories through this connector.
* **No stored credential:** The connection does not use an API key, OAuth grant, or other customer secret.
* **Reviewed tool set:** Rootly exposes only the three public repository tools listed above.
* **On-demand queries:** Rootly AI queries DeepWiki when an investigation or direct question needs repository context.
* **Data sent to Cognition:** Repository identifiers and free-text questions are processed by Cognition through DeepWiki.
* **Redacted session history:** Raw tool results and the response derived from them are available during the active investigation but are replaced with omission markers in durable AI session history.
* **Quality traces:** Connector results can appear in retained large language model (LLM) traces used for quality monitoring. See [Data Privacy for Rootly AI](/ai/data-privacy-for-rootly-ai) for the retention boundary.

***

## Managing the Connection

Open the DeepWiki card to disconnect it. Disconnecting prevents future DeepWiki queries and requires no credential revocation in Cognition.

To reconnect, click **Connect** again. Rootly validates DeepWiki's hosted endpoint and reviewed tools again before marking the connector as connected.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="DeepWiki cannot find the repository" icon="magnifying-glass">
    Confirm the repository is public on GitHub and enter its full `owner/repo` name. Forks and similarly named repositories can produce different documentation, so include the exact owner.
  </Accordion>

  <Accordion title="The repository is public but its wiki is unavailable" icon="book-open">
    Newly published or recently renamed repositories may not have generated documentation available yet. Confirm the repository opens on GitHub, then try again later. Use the Devin connector if the repository is private.
  </Accordion>

  <Accordion title="An answer is too broad or misses the incident context" icon="circle-question">
    Name the repository, component, observed symptom, and relevant error or operation in the question. Ask Rootly AI to inspect the wiki structure first when you do not know how DeepWiki organizes the repository.
  </Accordion>

  <Accordion title="DeepWiki queries time out" icon="clock">
    Narrow the question to one repository and component, then retry. Broad architecture questions can take longer because DeepWiki generates an answer from multiple parts of the codebase.
  </Accordion>
</AccordionGroup>

***

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Can DeepWiki read a private GitHub repository?" icon="lock">
    No. DeepWiki's public MCP endpoint works only with public GitHub repositories. Use the separate Devin connector for repositories available to your Devin organization.
  </Accordion>

  <Accordion title="Do I need a Devin account or API key?" icon="key">
    No. DeepWiki is a no-authentication connector. Click **Connect** in Rootly without creating or storing a Cognition credential.
  </Accordion>

  <Accordion title="Can DeepWiki change a repository?" icon="shield">
    No. The reviewed tools read generated documentation and answer questions. They cannot create branches, change files, open pull requests, or launch a Devin session.
  </Accordion>

  <Accordion title="Why are DeepWiki and Devin separate connectors?" icon="code-branch">
    DeepWiki provides no-authentication access to public repository knowledge. Devin uses your organization's service-user credential and can access repositories and platform actions allowed by that account. Keeping them separate lets your team choose the appropriate access boundary.
  </Accordion>
</AccordionGroup>

***

## Related Pages

<CardGroup cols={3}>
  <Card title="Devin" icon="robot" href="/ai/connectors/devin">
    Add authenticated repository knowledge and authorized Devin platform actions.
  </Card>

  <Card title="Connectors" icon="sparkles" href="/ai/connectors/overview">
    Browse all Rootly AI connectors and how investigations use them.
  </Card>

  <Card title="DeepWiki MCP" icon="arrow-up-right-from-square" href="https://docs.devin.ai/work-with-devin/deepwiki-mcp">
    Review Cognition's DeepWiki MCP tools and client configuration.
  </Card>
</CardGroup>