DeepWiki MCP MCP integration
Lists a repository's documentation topics, reads the wiki page behind one, and answers a direct question across up to ten public repos.
3actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ask question
Lyro asks AI-powered questions about a GitHub repository to uncover integration details. Your team gets context-grounded technical answers without diving into code.
Read wiki contents
Lyro reads documentation about a GitHub repository to answer technical questions. Your team accesses setup guides and API docs instantly.
Read wiki structure
Lyro retrieves a list of documentation topics for a repository to map learning paths. Your team finds the right docs section without searching blindly.
How businesses use DeepWiki MCP + Lyro
Each card is one request a support team gets, and the DeepWiki MCP actions Lyro runs to close it.
Answer a codebase question from a public repo's documentation
Lyro pulls the list of documentation topics for an owner/repo, reads the wiki page that covers the question, and asks DeepWiki directly when the answer needs more than one page provides.
Read Wiki StructureRead Wiki ContentsAsk Question
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the DeepWiki MCP actions it has and picks the ones a request needs.
- 01
Connect DeepWiki MCP
Authorize the DeepWiki MCP account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the DeepWiki MCP actions that close it and chains as many as the request needs.
- 03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Everything else about DeepWiki MCP
Setup, permissions, and the limits of what Lyro can do inside DeepWiki MCP.
No. DeepWiki MCP covers public GitHub repositories, so a private or internal repo returns nothing whatever credentials sit on the connected account. Lyro reports that the repository is not available rather than answering from guesswork.
Every action available in DeepWiki MCP
All 3 actions your agent can call on DeepWiki MCP, straight from the live MCP connection.
Ask question
Ask any question about a GitHub repository and get an AI-powered, context-grounded response.
Read wiki contents
View documentation about a GitHub repository.
Read wiki structure
Get a list of documentation topics for a GitHub repository.
The tools DeepWiki MCP sits next to
Same connection, same setup. Pick the next one your team already uses.
Browserless
Fetches rendered HTML, extracts elements by CSS selector, captures screenshots and PDFs, and runs custom Puppeteer scripts against live pages.
Daytona
Creates sandboxes with the repo cloned in, runs commands and returns logs, sets autostop intervals, and handles access from invite to SSH key.
Hackernews
Searches Hacker News discussions, resolves ranked story IDs into readable items, and reads Ask HN, Show HN, job, and user feeds.
Pagerduty
Reports who is on call, opens incidents and posts status updates, merges duplicates, and pages responders through a response play.
Shortpixel
Optimizes images in batches of 100, reports where a queued image stands, and manages the domains and credits behind the ShortPixel CDN.
Zenrows
Fetches a page as HTML, plaintext, or parsed JSON, captures screenshots and PDFs, and reports remaining credits and concurrency.
Ready to connect DeepWiki MCP?
Authorize the account and your agent has all 3 actions from the first conversation.