Remind MCP

remind-mcp

MCP server for Remind — read your classes, chats and messages, and manage notification settings.

This project was developed and is maintained by AI. Use at your own discretion.

Remind exposes a single GraphQL endpoint that is reachable server-side, so only the *credential* needs a browser: the session is lifted once from a signed-in tab through the ContextMint Bridge browser extension, and every request after that is a plain server-side fetch.

Install

npx -y @chrischall/remind-mcp

{

"mcpServers": { "remind": { "command": "npx", "args": ["-y", "@chrischall/remind-mcp"] } } }

Authentication

Two headers are captured from a signed-in remind.com tab: the full Cookie header and the x-csrf-token value. Either let the bridge capture them (needs the ContextMint Bridge browser extension and a signed-in tab), or supply them yourself:

Install ContextMint Bridge from its releases page: in Chrome, unzip the Chrome build and load it unpacked (chrome://extensions → Developer mode → Load unpacked). Safari isn't available yet (it will ship inside the ContextMint app, which has no public download), so use Chrome for now.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at https://github.com/nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256).

The server boots without either, so a host's install-time tools/list probe succeeds; the error surfaces on the first tool call instead.

The browser is needed once. A captured session is cached (mode 0600) and reused across restarts, and every call after the bootstrap is a plain server-side fetch. This matters because the capture completes only while the signed-in tab is actually issuing a /graphql request — so without the cache, a restart would sit waiting unless you happened to be using Remind.

The cache is bounded: analytics and consent cookies are dropped from the jar before it is used or stored, the record is bound to the Remind account (me.uuid) it authenticated as when captured — a restored session that answers as a different account, or as none, is discarded and re-captured — and it is re-captured from the browser after at most 7 days. An env-supplied session is never restored from the cache.

Tools

Confirmations

Write tools ask you to confirm before anything is sent. A client that can show a confirmation prompt (Claude Code) shows one. Otherwise the first call makes no network call and returns a preview of the exact payload plus a confirmToken; only a repeat call with that token (and the same arguments) performs the write. A token works once, and changing any argument between the two calls voids it.

Without the server

skills/remind-fpx/ is a shell-only skill covering the same read surface with fpx + curl — no MCP process required.

Notes

• An expired session returns HTTP 200 with errors[0].message = "Unauthorized"; the same string also means "your account may not do that" (scheduled messages are owner/teacher-only).
• An unknown field reports as Internal service error, not a field error — introspect rather than guess. docs/REMIND-API.md is the capture log.

Development

npm install && npm run build && npm test

npm run test:coverage

License

MIT