DeepWiki
Read and ask questions about any public GitHub repository's documentation through the DeepWiki MCP server.
Connect it with: MCP. DeepWiki's own documentation: https://docs.devin.ai/work-with-devin/deepwiki-mcp.
What agents can do
Connect DeepWiki so the agents working your tasks can reach it. With it connected, they can:
- Read the structure and pages of a public repository's DeepWiki before integrating with it.
- Ask a question about how a public open-source project works and get an answer grounded in its code.
Before you start
- Nothing to sign up for: the server is free and open. An Org Owner or Admin adds the secret once, then links it on each project's MCP tab.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with DeepWiki
Jaah connects to DeepWiki with the method below, not with a sign-in button.
Connect with an API key
DeepWiki has no API key option in Jaah: connect with the sign-in above.
Use your own OAuth app
Not used: Jaah connects to DeepWiki with the method above, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to DeepWiki with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
Tell the agent in your task description which secret to use, for example “use the DeepWiki secret org/deepwiki”.
Link DeepWiki's MCP server to a project
DeepWiki also runs an MCP server, which gives agents ready-made DeepWiki tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:
- Open the project and its MCP tab.
- Select Link, pick the DeepWiki secret, and confirm.
- New tasks on the project start with the DeepWiki tools. Tasks already running keep the tools they started with.
Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at DeepWiki's side too, revoke the access at DeepWiki.
Limitations
- Public GitHub repositories only; private repositories need Devin's own MCP server and a Devin API key (add it as a Custom MCP server).
- Agents get DeepWiki only in the projects the secret is linked to.
- Agents can do only what the connected DeepWiki account allows.
Troubleshooting
Test cannot complete the MCP handshake
DeepWiki is unreachable or changed its endpoint. Check https://docs.devin.ai/work-with-devin/deepwiki-mcp and try again later.
An agent gets no answer for a repository
The repository is private or DeepWiki has not indexed it yet. Open https://deepwiki.com and request the repository.
New tasks on the project have no DeepWiki tools
Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.
Still stuck? Select Test and read the result: it names the value DeepWiki refused and the status it answered.
FAQ
Why add a secret for a server with no key?
The secret is the connection a project links. It holds no key here, but it decides which projects' agents get DeepWiki's tools.
What does Test do?
It opens an MCP session with DeepWiki's server and lists its tools, then closes the session.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one DeepWiki account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.