Kani MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WANIKANI_API_TOKEN | Yes | Personal WaniKani API v2 bearer token with read-only permissions, created in the WaniKani API Tokens settings page. Required. | |
| WANIKANI_API_BASE_URL | No | API root; defaults to https://api.wanikani.com/v2. Changing the base URL sends the bearer token to that host. Remote overrides must use HTTPS; localhost HTTP is accepted for tests and local development. | https://api.wanikani.com/v2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Get the authenticated WaniKani user profile and subscription state |
| get_summaryA | Get lesson and review availability for the next 24 hours |
| list_level_progressionsC | List level progression history |
| list_resetsC | List account reset history |
| list_reviewsC | List completed reviews |
| list_spaced_repetition_systemsC | List spaced repetition system definitions |
| list_study_materialsC | List user notes and synonyms |
| list_voice_actorsC | List pronunciation voice actors |
| list_assignmentsC | List assignments with optional subject, level, SRS, and availability filters |
| list_review_statisticsC | List accuracy statistics for studied subjects |
| list_subjectsB | List radicals, kanji, and vocabulary with optional level, type, or slug filters |
| get_resourceA | Get one WaniKani resource by type and numeric ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
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.
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.
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.
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.