Remind MCP server

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 fetchproxy bridge, 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 Transporter Chrome extension and a signed-in tab), or supply them yourself:

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.

Tools

Write tools take confirm: true. Without it they make no network call and return a dry-run preview of the exact payload.

Without the server

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

Notes

string also means "your account may not do that" (scheduled messages are owner/teacher-only).

• An expired session returns HTTP 200 with errors[0].message = "Unauthorized"; the same

than guess. docs/REMIND-API.md is the capture log.

• An unknown field reports as Internal service error, not a field error — introspect rather

Development

npm install && npm run build && npm test
npm run test:coverage

License

MIT