waterloo-mcp

An MCP server with read-only access to your University of Waterloo accounts.

Nothing here submits, posts or changes anything. Files and images come back as content the model can read.

Sign in

pip install -r requirements.txt playwright && playwright install chromium
python login.py                         # add --email you@uwaterloo.ca to have it fill the UW and Piazza sign-in forms

A browser opens; sign in to each service as usual, Duo included. The session cookies are saved to data/. Your password never leaves that browser. When a session eventually expires, sign_in_status says so; run login.py again.

Related MCP server: UWaterloo MCP

Use it locally

Add it to any MCP client as a stdio server, e.g. Claude Code:

claude mcp add waterloo -- python /path/to/waterloo-mcp/server.py

Host it

To reach it from anywhere (phone, web), run it over HTTP behind any HTTPS reverse proxy. Fill in .env from .env.example (your URL, and a GitHub, Google or Discord OAuth app so only you can sign in), then:

docker compose up -d
python login.py --push <ssh-host>:<path-to-this-folder>

--push sends the cookies straight into the container and keeps no local copy. Add https://<your-domain>/mcp to your client as a remote server. Hosted, every file also gets a one-time download link that streams through the server without touching disk.

Sign in automatically (optional)

To stop running login.py whenever a session ends, let the server sign in again by itself. This stores your passwords on the server, so only do it on a machine you trust.

cp login.env.example login.env && chmod 600 login.env   # fill in your UW (and optionally Piazza) sign-in
echo AUTOLOGIN=1 >> .env
docker compose --profile autologin up -d

A second container keeps a headless browser. When a service signs out, it signs in with your saved passwords and the server picks up the new cookies without a restart. UW still needs Duo: approve the push on your phone. If Duo asks for a code, sign_in_status and docker compose logs autologin show it. It tells Duo to remember its browser, so most sign-ins skip the push. It signs in at most every 15 minutes and backs off while sign-in keeps failing, so a wrong password can't lock you out. Only that container reads login.env; the MCP server never sees your passwords. Leave Piazza blank to keep signing in to it with login.py.

Contributing

Issues and PRs welcome, including from agents using the server.

Credits: the WaterlooWorks protocol is from waterloo-works-scraper; Piazza method names follow piazza-api.