knu-mcp
Related Servers
Alternatives to knu-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that aggregates department notices and provides structured answers to queries about courses, schedules, and academic dates via tool calling.-
- AlicenseAqualityAmaintenanceRead-only MCP server that lets Jeonbuk National University students query their LMS in natural language, covering daily briefings, deadlines, announcements, assignments, and course materials while keeping credentials local.2522 npmMIT
- AlicenseCqualityCmaintenanceMCP server that reads Korean school class and teacher timetables from Comci's public schedules, detects schedule changes, and exposes structured data via CLI, local REST, and MCP stdio.81Academic Free v1.1
- FlicenseNot gradedqualityCmaintenanceMCP server for searching and retrieving Korean contest information. Provides tools to search contests by keyword/category, get details, list categories, and find deadlines.-
- AlicenseNot gradedqualityBmaintenanceAn unofficial, local, read-only MCP server that integrates Waseda University's Moodle, class cancellation info, syllabus, and academic calendar, enabling users to query their classes, deadlines, changes, and syllabi with source citations.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Korean school budget, unit projects, and special plans through the School Alert (학교알리미) open data API.MIT
TDQS
Scored across 7 tools
Most tools target distinct resources: notices, bus arrivals, academic calendar, etc. The main overlap is between get_cafeteria_menu and get_all_cafeteria_menus (single vs. all restaurants), and between get_next_shuttle and get_shuttle_schedule (next departure vs. full timetable), but the descriptions make these differences clear.
The naming pattern is predominantly get_<noun>, with one search_notices exception. All names use lower_snake_case and are readable, but the mix of 'get' and 'search' plus the get_ vs get_all_ prefix variation creates minor inconsistency.
Seven tools is well within the ideal 3-15 range for a university information server. Each tool addresses a distinct user need (meals, notices, shuttles, city buses, calendar) without redundancy or bloat.
The tool surface covers the main information needs for the university domain: cafeteria, shuttle, bus, notices, and academic calendar. Minor gaps exist, such as no direct route info for shuttles or detailed notice content retrieval, but these are workable limitations rather than critical dead ends.