Skip to main content
Glama

Related Servers

Alternatives to Kani MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      A read-only Model Context Protocol server that lets MCP clients view a user's Bunpro profile, review queue, forecasts, SRS progress, vocabulary, learning content, and search results. It also exposes study statistics and read-only quiz data without account-changing or review-submission tools.
      22
      83 npm
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      A local MCP server that helps you maintain a personal Japanese learning knowledge base, including vocabulary, confusion relations, mistakes, and spaced-repetition reviews. It provides tools and prompts for managing and reviewing your Japanese learning data without calling external LLM APIs.
      6
      -
    • A
      license
      A
      quality
      C
      maintenance
      Local, read-only-by-default MCP server for Weeek that connects AI clients to your workspace over stdio, enabling listing projects, tasks, boards, members, and tags with opt-in write tools for task management.
      10
      59 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An unofficial MCP server for Bunpro that exposes its review queue, search, statistics, and SRS management as tools, enabling an LLM agent to read study data and add grammar points or vocabulary to reviews.
      23
      2 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that lets ChatGPT inspect your LingQ progress without exposing your password. It exposes tools for listing languages, checking progress capabilities, and retrieving progress summaries and charts.
      -

    TDQS

    B3.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource (user, summary, resets, voice actors, subjects, assignments, study materials). The main soft spots are the cluster of review-related tools (list_reviews vs list_review_statistics vs list_assignments with availability filters) and get_resource, which is a generic fetch that overlaps conceptually with every list_* and get_user.

    Naming Consistency5/5

    Every tool follows a strict snake_case verb_noun pattern using only get_ and list_ prefixes, matching the read-only nature of the surface. No camelCase mixing or vague verb-only names.

    Tool Count5/5

    12 tools is squarely in the well-scoped range and each one maps to a distinct WaniKani endpoint family. Nothing feels padded or redundant given the breadth of the WaniKani API.

    Completeness3/5

    Coverage is solid for reading (profile, availability, subjects, assignments, reviews, stats, SRS, study materials), but the surface is entirely read-only: there is no way to create a review, start an assignment, or create/update study materials, which are core lifecycle operations in this domain. Agents can explore but cannot act.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues