DTU Learn MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DTU_LEARN_URL | No | URL of another Brightspace site instead of DTU Learn (untested). | |
| DTU_LEARN_BROWSER | No | Browser used for sign-in, e.g. 'chrome' or 'msedge'. | |
| DTU_LEARN_DOWNLOAD_DIR | No | Directory where downloaded files are saved (files you ask about are downloaded to ~/.dtu-learn-mcp/files/ by default). |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusA | Checks whether you are signed in to DTU Learn and shows who you are signed in as. Use this first if other tools report authentication problems. |
| loginA | Signs in to DTU Learn. Only call this when other tools say the user is not signed in. If the user turned on automatic sign-in (saved password) this happens without a window; otherwise it opens a browser window on the user's computer where they sign in themselves (DTU login + MFA), so tell the user to look for it. Waits up to 5 minutes. |
| list_coursesA | Lists the user's DTU Learn courses (current semester by default) with their ids. Use the course number or id with the other tools. |
| get_course_outlineA | Shows a course's content tree (modules, lecture folders, slides, files, links, quizzes) with topicIds. Use |
| get_upcomingA | Lists deadlines and dated items in the next N days across all courses (or one course): assignment due dates, quizzes, content with dates, and calendar events, which at DTU include timetable lectures and group work with rooms. Good for 'what do I need to do this week?'. |
| list_assignmentsA | Lists a course's assignments (hand-in folders) with due dates and attachment counts, sorted by due date. |
| get_assignmentA | Shows an assignment's full instructions, attached files (with fileIds for read_file), links, rubric names, and the user's own submissions (with submissionFileIds for read_file) and feedback, including feedback files (with feedbackFileIds for read_file). |
| get_topicA | Shows details for one content item (topicId from get_course_outline): description, dates, and the URL for links, videos and external tools such as Panopto. Use read_file instead to read the contents of a file. |
| read_fileA | Downloads a file from DTU Learn to the user's computer and returns its text (PDF, PowerPoint incl. speaker notes, Word, notebooks, code, text). Give either topic_id (course content), assignment_id + file_id (assignment attachment), assignment_id + submission_file_id (a file the user handed in), assignment_id + feedback_file_id (a file in the user's feedback, e.g. their hand-in with the teacher's comments), or url (a DTU Learn link to a file, as shown in module pages, descriptions and instructions, e.g. https://learn.inside.dtu.dk/content/enforced/...). Long files are paged: use offset to continue. The saved path is returned so a coding agent can also open the original. |
| get_announcementsB | Shows recent announcements (news) from all courses, newest first. |
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 10 tools
Each tool targets a distinct resource or action: authentication, course listing, outline navigation, upcoming deadlines, assignments, individual topics, file reading, announcements, and status. The potentially overlapping tools (get_upcoming vs. list_assignments, get_topic vs. read_file) are clearly differentiated by their descriptions.
Most tools follow a predictable verb_noun pattern such as list_courses, get_assignment, read_file, and get_announcements. A few utilities (login, status) deviate from that pattern, and get_upcoming omits a noun, but the overall convention is still readable and consistent.
Ten tools is well-scoped for an LMS access server, covering authentication, courses, content, assignments, files, deadlines, and announcements without obvious filler. Each tool earns its place in the workflow.
The surface covers core student read workflows: sign-in, course discovery, content browsing, assignment details, file reading, deadlines, and announcements. Minor gaps remain, such as assignment submission or grade retrieval, but agents can work around most of these for the stated access-oriented purpose.