Skip to main content
Glama
ai-vivid

DeepWiki MCP Server

by ai-vivid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to DeepWiki MCP Server

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      maycwu
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to GitHub repositories for querying repos, reviewing PRs, managing issues, searching code, and automating workflows.
      MIT

    • GitHub Insights MCP Server

      AhmetSOGUT
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to analyze any public GitHub repository through typed, focused tools that surface metadata, README content, file structure, detected tech stack, and Mermaid architecture diagrams. It lets users explore repo purpose, structure, and dependencies via natural language without manual browsing.
      MIT

    • GitHub Context MCP Server

      Haavi97
      F
      license
      A
      quality
      D
      maintenance
      Enables Claude to access and manage GitHub repositories dynamically at runtime, including private repos, with tools for browsing files, searching code, and viewing commits, pull requests, and issues.
      11
      1
      -

    • Repo Recap

      AbhiShrek07
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to query GitHub repositories in plain English, fetching recent activity, release notes, issue triage, and health summaries via the GitHub API.
      -

    • GitHub MCP Server

      shibdad
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Claude Desktop to GitHub repositories, enabling users to perform git operations and GitHub API interactions through natural conversation.
      245 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have distinct primary purposes: wiki_parser for navigation and extraction of documentation structure/content, and wiki_question for asking questions and retrieving code references. There is some overlap in that both can retrieve textual content, but the descriptions clearly differentiate the intended use cases, so an agent is unlikely to misselect.

    Naming Consistency5/5

    Both tools follow a consistent pattern of 'wiki_' followed by a noun (parser, question). This is a predictable and coherent naming convention that makes the tool roles clear and easy to remember.

    Tool Count3/5

    With only two tools, the server feels thin for the broad feature set described. Each tool is highly configurable and covers many sub-features, which partially compensates, but the count is below the typical 3-15 range and borders on insufficient for a comprehensive documentation access server.

    Completeness4/5

    The two tools cover the main operations for DeepWiki: extracting documentation structure and content, and asking questions with reference retrieval. Minor gaps exist, such as no explicit tool for listing available repositories or managing multiple documentation sessions, but these are likely handled at the server configuration level rather than being missing from the tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources