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:

| Variable | Required | Description | |---|---|---| | REMIND_COOKIE | no | Captured Cookie request header. Skips the bridge when set with the next one; once Remind rejects the pair as expired, the server falls back to the bridge (or, without one, tells you to refresh both). | | REMIND_CSRF_TOKEN | no | Captured x-csrf-token value. | | REMIND_WS_PORT | no | fetchproxy bridge concentrator port (default 37149). | | REMIND_SESSION_FILE | no | Where the captured session is cached. Defaults to $MCP_DATA_DIR/$HOME under .remind-mcp. |

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-<version>.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

| Tool | | |---|---| | remind_me | The signed-in account. | | remind_list_entities | Classes and chats with unread counts — start here, it yields the uuids. | | remind_get_classes | Full class detail by uuid. | | remind_list_chats | Conversation streams and their permissions (canSend). | | remind_get_messages | Messages in a chat stream. | | remind_get_notification_settings | Preferences and delivery devices. | | remind_set_notification_devices | Enable/disable delivery devices. Asks you to confirm first. | | remind_send_message | Send to a chat or class. Asks you to confirm first. | | remind_graphql | Arbitrary read-only GraphQL; introspection is enabled. Mutations refused. | | remind_healthcheck | Verify the session still authenticates; on failure error.kind names the broken hop (no_credential, credential_rejected, edge_blocked, http, timeout, transport). |

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.

| variable | default | | |---|---|---| | MCP_CONFIRM_MODE | ask-user | What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse. | | MCP_CONFIRM_ELICITATION | on | off never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE behaviour. Set it for a client that says it can show prompts but never does (the write hangs — opencode 2.0.x). Any other value is treated as on, with a warning on stderr. | | MCP_CONFIRM_TTL_SECONDS | 600 | How long a token stays valid. | | MCP_CONFIRM_SECRET | random per process | Signing key; set it only if tokens must survive a server restart. On mcp-host the host supplies a stable per-child key (MCP_HOST_CONFIRM_SECRET) and spent tokens are recorded under MCP_DATA_DIR, so an approval survives an idle restart. |

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