brightspace-mcp-server 3.9.2 → 3.9.3

package/README.md

@@ -178,6 +178,21 @@ If this is a Docker or other headless setup with no `~/.brightspace-mcp/config.j
 | Calendar | "When is my midterm?" · "What's on my calendar this week?" · "Is lab cancelled on Thursday?" — reads exams, labs, review sessions, and deadlines instructors put only on the course calendar |
 | Planning | "Build me a study schedule based on my upcoming due dates" · "Which class needs the most attention right now?" — pulls from assignments, quizzes, graded discussion topics (any topic with a due date), and course calendar events such as exams and labs |
 
+### Prompts
+
+Clients that show server-provided prompts (e.g. Claude Desktop's prompt picker) can also start from one of
+four canned prompts instead of typing a question from scratch:
+
+| Prompt | Arguments | What it asks for |
+|--------|-----------|-------------------|
+| `weekly_briefing` | — | A 7-day rollup of what's due, what's new, and what's changed in grades, across every course |
+| `grade_audit` | `courseId` (optional) | Analyzes grades for one course, or all of them, and flags missing or low-scoring items |
+| `study_planner` | `daysAhead` (optional, default 7) | Plans study time from upcoming due dates and calendar events |
+| `course_summary` | `courseId` (required) | Syllabus, content outline, assignments, and grades for one course |
+
+Each prompt is a single starter message built from the tools above — it doesn't add any new capability on
+its own, just a one-click way to ask for a common combination of them.
+
 `get_course_content` reports `isAvailable`, `availabilityStatus` (`available`, `not_yet_open`, `ended`, `hidden`, or `locked`), `availabilityMessage`, `startDate`, and `endDate` for modules and topics. The effective release window includes restrictions inherited from enclosing modules.
 
 When a content-file download returns 403 or 404, `download_file` checks topic metadata and the course table of contents. Confirmed restrictions return `{ success: false, available: false, reason, message, startDate, endDate }` so the assistant can explain when content opens or why it has closed. Unexplained 404s and server/network failures retain their original errors.

package/build/index.js

@@ -17,6 +17,7 @@ import { readFileSync } from "node:fs";
 import { fileURLToPath } from "node:url";
 import { dirname, resolve } from "node:path";
 import { registerGetMyCourses, registerGetUpcomingDueDates, registerGetCalendarEvents, registerGetMyGrades, registerGetAnnouncements, registerGetAssignments, registerGetAssignmentFiles, registerGetAnnouncementFiles, registerGetCourseContent, registerDownloadFile, registerGetClasslistEmails, registerGetRoster, registerGetSyllabus, registerGetDiscussions, registerGetVideoTranscript, registerGetServerInfo, } from "./tools/index.js";
+import { registerWeeklyBriefingPrompt, registerGradeAuditPrompt, registerStudyPlannerPrompt, registerCourseSummaryPrompt, } from "./prompts/index.js";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
 const PKG_VERSION = (() => {
@@ -132,10 +133,19 @@ else {
             registerGetVideoTranscript(server, apiClient);
             registerGetServerInfo(server, config, PKG_VERSION, apiClient);
             log("DEBUG", "MCP tools registered (16 tools)");
+            // Register MCP prompts — surfaced in clients (e.g. Claude Desktop) as a
+            // picker, distinct from tools. Each one is a canned user message that
+            // names our own tools by name, so a client with no idea what to ask
+            // for still gets a one-click starting point.
+            registerWeeklyBriefingPrompt(server);
+            registerGradeAuditPrompt(server);
+            registerStudyPlannerPrompt(server);
+            registerCourseSummaryPrompt(server);
+            log("DEBUG", "MCP prompts registered (4 prompts)");
             // Connect stdio transport
             const transport = new StdioServerTransport();
             await server.connect(transport);
-            log("INFO", "Brightspace MCP Server by Rohan Muppa — running on stdio (16 tools registered)");
+            log("INFO", "Brightspace MCP Server by Rohan Muppa — running on stdio (16 tools, 4 prompts registered)");
             log("INFO", "Setup: see README.md for MCP client configuration (Claude Desktop, ChatGPT Desktop, Cursor, etc.)");
         }
         catch (error) {

package/build/prompts/course-summary.js

@@ -0,0 +1,41 @@
+/**
+ * Purdue Brightspace MCP Server
+ * Copyright (c) 2026 Rohan Muppa. All rights reserved.
+ * Licensed under MIT — see LICENSE file for details.
+ */
+import { z } from "zod";
+/**
+ * Register the course_summary prompt.
+ *
+ * `courseId` is required — unlike the other three prompts this one is
+ * always about exactly one course, so there is no sensible "all courses"
+ * fallback the way get_my_grades or get_assignments have.
+ */
+export function registerCourseSummaryPrompt(server) {
+    server.registerPrompt("course_summary", {
+        title: "Course Summary",
+        description: "A one-course rollup: syllabus, content outline, assignments, and current grades.",
+        argsSchema: {
+            courseId: z.coerce
+                .number()
+                .int()
+                .positive()
+                .describe("Course ID to summarize."),
+        },
+    }, async (args) => ({
+        messages: [
+            {
+                role: "user",
+                content: {
+                    type: "text",
+                    text: `Give me a summary of course ${args.courseId}. Call get_syllabus for the course ` +
+                        `description and policies, get_course_content for the module and topic outline, ` +
+                        `get_assignments for what's assigned and its due dates and submission status, and ` +
+                        `get_my_grades for where I currently stand. Pull it together into one summary: what ` +
+                        "the course covers, how it's structured, what's outstanding, and how my grades look " +
+                        "so far.",
+                },
+            },
+        ],
+    }));
+}

package/build/prompts/grade-audit.js

@@ -0,0 +1,48 @@
+/**
+ * Purdue Brightspace MCP Server
+ * Copyright (c) 2026 Rohan Muppa. All rights reserved.
+ * Licensed under MIT — see LICENSE file for details.
+ */
+import { z } from "zod";
+/**
+ * Register the grade_audit prompt.
+ *
+ * `courseId` is optional, same as the tools it drives (get_my_grades,
+ * get_assignments): omitted, it audits every enrolled course at once.
+ */
+export function registerGradeAuditPrompt(server) {
+    server.registerPrompt("grade_audit", {
+        title: "Grade Audit",
+        description: "Analyze grades for one course or all of them, flagging missing, ungraded, or low-scoring items.",
+        argsSchema: {
+            courseId: z.coerce
+                .number()
+                .int()
+                .positive()
+                .optional()
+                .describe("Course ID to audit. If omitted, audits every enrolled course."),
+        },
+    }, async (args) => {
+        const scope = args.courseId !== undefined
+            ? `course ${args.courseId}`
+            : "every enrolled course";
+        const courseArg = args.courseId !== undefined ? `courseId: ${args.courseId}` : "no courseId (all courses)";
+        return {
+            messages: [
+                {
+                    role: "user",
+                    content: {
+                        type: "text",
+                        text: `Audit my grades for ${scope}. Call get_my_grades with ${courseArg} and ` +
+                            `get_assignments with ${courseArg} and cross-reference them: flag any assignment ` +
+                            "or quiz with no grade posted yet, anything graded well below the class or my own " +
+                            "average, and any gradebook column from get_my_grades that matches no assignment " +
+                            "(a gradeOnly item, such as a proctored exam). If no courseId was given, first call " +
+                            "get_my_courses so you can label every finding with its course name, and summarize " +
+                            "per course before giving an overall picture.",
+                    },
+                },
+            ],
+        };
+    });
+}

package/build/prompts/index.js

@@ -0,0 +1,10 @@
+/**
+ * Purdue Brightspace MCP Server
+ * Copyright (c) 2026 Rohan Muppa. All rights reserved.
+ * Licensed under MIT — see LICENSE file for details.
+ */
+// Prompt registration functions - barrel export
+export { registerWeeklyBriefingPrompt } from "./weekly-briefing.js";
+export { registerGradeAuditPrompt } from "./grade-audit.js";
+export { registerStudyPlannerPrompt } from "./study-planner.js";
+export { registerCourseSummaryPrompt } from "./course-summary.js";

package/build/prompts/study-planner.js

@@ -0,0 +1,52 @@
+/**
+ * Purdue Brightspace MCP Server
+ * Copyright (c) 2026 Rohan Muppa. All rights reserved.
+ * Licensed under MIT — see LICENSE file for details.
+ */
+import { z } from "zod";
+/**
+ * Register the study_planner prompt.
+ *
+ * `daysAhead` mirrors get_upcoming_due_dates' own argument (same name,
+ * same default) so the window the user asks about and the window the
+ * underlying tool call uses never drift apart.
+ */
+export function registerStudyPlannerPrompt(server) {
+    server.registerPrompt("study_planner", {
+        title: "Study Planner",
+        description: "Plan study time from upcoming due dates and calendar events over the next N days (default 7).",
+        argsSchema: {
+            // .optional() (not just .default()) keeps this argument out of the
+            // "required" list in prompts/list — a bare .default() still shows up
+            // as required there even though a missing value falls back fine.
+            daysAhead: z.coerce
+                .number()
+                .int()
+                .min(1)
+                .max(90)
+                .optional()
+                .describe("Number of days ahead to plan for. Defaults to 7."),
+        },
+    }, async (args) => {
+        // args is undefined when the SDK's no-args path reaches this callback
+        // for all-optional schemas; args.daysAhead is undefined when the field
+        // itself was omitted. Either way, fall back to 7.
+        const days = args?.daysAhead ?? 7;
+        return {
+            messages: [
+                {
+                    role: "user",
+                    content: {
+                        type: "text",
+                        text: `Build me a study plan for the next ${days} days. Call ` +
+                            `get_upcoming_due_dates with daysAhead: ${days} for assignments, quizzes, ` +
+                            `and discussion due dates, and get_calendar_events for the same window to pick up ` +
+                            "exams, labs, and other scheduled events. Group the work by day, put the heaviest or " +
+                            "most time-sensitive items earliest, leave a buffer day before anything that looks " +
+                            "like an exam, and call out any day with more due than looks reasonable to finish.",
+                    },
+                },
+            ],
+        };
+    });
+}

package/build/prompts/weekly-briefing.js

@@ -0,0 +1,41 @@
+/**
+ * Purdue Brightspace MCP Server
+ * Copyright (c) 2026 Rohan Muppa. All rights reserved.
+ * Licensed under MIT — see LICENSE file for details.
+ */
+/**
+ * Register the weekly_briefing prompt.
+ *
+ * Takes no arguments: it asks for a rolled-up status of the coming week
+ * across every enrolled course, which is exactly the kind of thing a user
+ * opens their client just to ask, every Monday, without typing it out.
+ */
+export function registerWeeklyBriefingPrompt(server) {
+    server.registerPrompt("weekly_briefing", {
+        title: "Weekly Briefing",
+        description: "A 7-day rollup of what's due, what's new, and what's changed in grades across every enrolled course.",
+        // No argsSchema: this prompt takes no arguments. An empty `argsSchema: {}`
+        // would make the SDK validate `request.params.arguments` against
+        // z.object({}), which rejects a GetPrompt call that omits `arguments`
+        // entirely (some MCP clients do). Omitting argsSchema takes the SDK's
+        // no-args path instead, which accepts both a missing and an empty
+        // `arguments` field.
+    }, async () => ({
+        messages: [
+            {
+                role: "user",
+                content: {
+                    type: "text",
+                    text: "Give me a briefing for the next 7 days across all my Brightspace courses. " +
+                        "Use get_upcoming_due_dates (daysAhead: 7) for what's due, get_calendar_events " +
+                        "(the next 7 days) for exams, labs, and other scheduled events, " +
+                        "get_announcements (modifiedSince: 7 days ago) for anything new course staff " +
+                        "posted, and get_my_grades to call out any grade that changed or any item that " +
+                        "newly posted a score. Organize the result by course, lead with anything due in " +
+                        "the next 48 hours, and flag announcements or grade changes that need a reply or " +
+                        "a decision from me.",
+                },
+            },
+        ],
+    }));
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "brightspace-mcp-server",
-  "version": "3.9.2",
+  "version": "3.9.3",
   "mcpName": "io.github.rohanmuppa/brightspace",
   "description": "MCP server for Brightspace (D2L). Check grades, due dates, assignments, announcements, syllabus, rosters and more via Claude, ChatGPT, Cursor, Windsurf, or any MCP client.",
   "type": "module",