Waseda Moodle MCP

English · 日本語 · 简体中文

Connect Waseda University Moodle (wsdmoodle) to Claude, ChatGPT, Cursor and other AI assistants. Assignments & deadlines, timetable, syllabus, grades and course updates — just ask.

Public instance · Self-hosting · MIT License

An MCP (Model Context Protocol) server for Waseda University's Moodle (https://wsdmoodle.waseda.jp). Ask your AI assistant what is due this week, when and where your next class is, how a course is graded, or what teachers posted recently — across every course at once. It is Waseda-only by design: the Moodle origin, the login flow and several features (syllabus-based timetable, assignments & deadlines sweep) are specific to that site.

It runs either as a hosted service on Cloudflare Workers (with a web console) or as a local stdio process. Unofficial; not affiliated with Waseda University.

Ask things like

• "What assignments are due this week? Which ones have I not submitted?"

• "What classes do I have tomorrow, and in which rooms?"

• "How is Introduction to Data Science graded?"

• "What did teachers add to my courses since Monday?"

Screenshots

Screenshots use fictional demo data.

Related MCP server: mcp-moodle

Features

Assignments & deadlines

• Outstanding items grouped Overdue / Today / Tomorrow / Next 7 days / Later, or by course (group_by=course). Submitted items stay in their group struck through. From the Moodle calendar plus a background sweep that finds undated activities and deadlines written in course text (marked "verify").

• Recent teacher additions and changes in your courses.

• Calendar feed: a secret ICS subscription URL (console Settings → Calendar feed) for assignments & deadlines and the timetable in Google Calendar, Apple Calendar or Outlook.

Timetable

• Per-day classes with times, room and campus, built from the public Waseda syllabus and the academic calendar. On-demand and unknown slots listed separately.

Courses, content and grades

• Enrolled courses (this term by default), a confirmed course selection (Settings → This term's courses), course sections and activities, activity details, name search across courses, grades per course.

Forums, messages and notifications

• Forum threads and posts, Moodle conversations, notifications with unread counts.

Files

• Download any Moodle file through a short-lived signed URL (hosted) or a temp file (stdio); small files can be attached inline.

Writes with preview, then confirm

• Assignment submission (text and files), forum posts and replies, Moodle messages, manual completion.

• Every write is two steps: prepare_* returns a preview, and nothing reaches Moodle until confirm_action runs after you agree. Writes can also be restricted to approval in the web console, or turned off.

How it works

The server talks to Moodle's web services using the same token the official Moodle mobile app uses. That token is obtained from Moodle's mobile-app launch flow while you are signed in to Moodle in your browser; your password is never requested or seen.

AI client  <-- MCP (HTTP or stdio) -->  MCP server (Worker / Node)  <-- REST -->  Moodle web services
                                              |
                                        D1 / KV (hosted)

Quick start

Public instance — operated by Konata, free:

1. Open the public instance and connect Moodle with the bookmarklet, the browser extension, or by pasting the launch link. Your password is never asked for.

2. Optionally confirm this term's courses under Settings → This term's courses.

3. Copy the MCP URL from Settings → AI clients and add it to your AI client (see Clients).

Your own instance — see Self-hosting. Below, https://wasemoodle.example.com stands for your instance URL.

Console

The hosted console sidebar: Overview, Assignments & deadlines, My courses, Timetable, Approvals, Settings.

My courses is the per-course view (tasks, timetable, syllabus grading, recent updates). Confirm which courses you attend under Settings → This term's courses.

Settings tabs: General, This term's courses, AI clients, API keys, Authorized apps, Calendar feed, Activity, Account.

Clients

MCP URL: https://wasemoodle.example.com/mcp (Streamable HTTP). OAuth is the default: the client discovers the authorization server from the 401 response (RFC 9728), registers itself and opens the consent page, where you grant read-only or read+write access. API keys (wmm_…, created on the console Settings → API keys) are for clients that can send an Authorization: Bearer <API_KEY> header. The console Settings → AI clients page shows the same steps with your instance URL filled in.

With an API key instead of OAuth. Keep the key out of project files: CLIs store it in your user config, and Codex and Cursor read it from WMM_API_KEY (set it in your shell profile, e.g. export WMM_API_KEY='<API_KEY>' in ~/.zshrc).

# Claude Code / Grok CLI (instead of the OAuth command; `claude mcp remove waseda-moodle` first if already added)
claude mcp add --transport http waseda-moodle https://wasemoodle.example.com/mcp \
  --header "Authorization: Bearer <API_KEY>"
grok mcp add --transport http waseda-moodle https://wasemoodle.example.com/mcp \
  --header "Authorization: Bearer <API_KEY>"
# Codex
codex mcp add waseda-moodle --url https://wasemoodle.example.com/mcp --bearer-token-env-var WMM_API_KEY

Cursor (~/.cursor/mcp.json): add "headers": { "Authorization": "Bearer ${env:WMM_API_KEY}" } to the server entry. VS Code (.vscode/mcp.json): let VS Code prompt for the key and store it securely:

{
  "inputs": [
    { "type": "promptString", "id": "wmm-api-key", "description": "Waseda Moodle MCP API key", "password": true }
  ],
  "servers": {
    "waseda-moodle": {
      "type": "http",
      "url": "https://wasemoodle.example.com/mcp",
      "headers": { "Authorization": "Bearer ${input:wmm-api-key}" }
    }
  }
}

Gemini CLI (~/.gemini/settings.json, use httpUrl): add "headers": { "Authorization": "Bearer <API_KEY>" } to the server entry. ChatGPT and Claude (web) use OAuth only.

Local stdio (Node 20+):

pnpm install
pnpm build:stdio                                  # produces dist/stdio.js
node dist/stdio.js connect -                      # paste the launch link on stdin

Client configuration (JSON form used by most clients):

{
  "mcpServers": {
    "waseda-moodle": {
      "command": "node",
      "args": ["/path/to/waseda-moodle-mcp/dist/stdio.js"]
    }
  }
}

Or with Claude Code: claude mcp add waseda-moodle -- node /path/to/dist/stdio.js --read-only.

Stdio stores the token in plain text (file mode 0600) and does not support console approval of writes or create_upload_link.

Tools

Prompts: daily_briefing (optional date), weekly_plan, exam_prep (course). Resources: moodle://course/{course_id} and moodle://syllabus/{course_id}. Prepared actions expire after 30 minutes. Times are shown in JST. The server never takes quizzes.

Security and privacy

• No Moodle password is ever requested. The Moodle token is encrypted at rest (AES-256-GCM with the operator's MASTER_KEY).

• File contents are streamed, not stored. Download and upload links are HMAC-signed and expire in 15 and 30 minutes.

• API keys are stored as hashes. OAuth access tokens last 12 hours, refresh tokens 90 days.

• Deleting your account under Settings → Account removes all of your data on the server.

Details: docs/privacy.md.

Self-hosting

The hosted variant fits the Cloudflare Workers Free plan (Worker + D1 + KV + static assets). See docs/self-hosting.md.

Development

Layout: src/core (runtime-agnostic services, Moodle client, MCP tools), src/worker (Cloudflare entry, OAuth, API, D1 store, cron), src/node (stdio CLI), web (React console), extension (MV3 connector, no build step), migrations (D1 SQL), tests.

License

MIT.

Disclaimer

This is an unofficial project and is not affiliated with or endorsed by Waseda University. The Moodle token it uses is the same token the official Moodle mobile app uses (one per user). This server never revokes or resets it; if Moodle rejects it, the server simply asks you to reconnect.