Log inSubmit server
Remind MCP logo

Remind MCP

Read Remind classes, chats, messages, notification settings, and send confirmed messages through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Remind MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "remind-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/remind-mcp"
      ],
      "env": {
        "REMIND_COOKIE": "YOUR_VALUE_HERE",
        "REMIND_CSRF_TOKEN": "YOUR_VALUE_HERE",
        "REMIND_WS_PORT": "YOUR_VALUE_HERE",
        "REMIND_SESSION_FILE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_MODE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_ELICITATION": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_TTL_SECONDS": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 10 tools correctly (Today).

Overview

remind-mcp connects MCP clients to Remind’s server-side GraphQL endpoint for account, class, chat, message, and notification operations. It captures a signed-in Remind session through the ContextMint Bridge browser extension or accepts captured credentials through environment variables, then caches and reuses the session for server-side requests. Start with entity discovery to obtain class and chat UUIDs before requesting details or messages. Use it when an agent needs to inspect Remind activity, manage delivery devices, or send messages with confirmation safeguards.

Use cases

  • Read unread classes and chats
  • Inspect messages in a Remind conversation
  • Review notification preferences and devices
  • Send a confirmed message to a class
  • Check whether the Remind session still authenticates

Key features

  • Class and chat discovery with unread counts
  • Message and class detail retrieval
  • Notification device management
  • Confirmed message sending
  • Read-only GraphQL with introspection
  • Session health checks and caching

Tools10

What Remind MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 56d

What it can do

From the 10 tools this server returned when we ran it; 10 declare their own safety hints.

Can delete or modify data · 1Handles credentials · 3Makes network requests · 10Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age66 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @chrischall/remind-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.9kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed10Callable tools this server registers over MCP.

How Remind MCP works

What remind-mcp does

remind-mcp exposes Remind account data and actions as MCP tools. It can identify the signed-in account, enumerate classes and chats with unread counts, retrieve class details, list chat streams and their sending permissions, and read messages. Notification tools expose preferences and delivery devices, including an operation to enable or disable devices.

The server also supports sending a message to a chat or class. Write operations require confirmation before making a network request. For broader read access, remind_graphql accepts arbitrary read-only GraphQL and permits introspection, while rejecting mutations. remind_healthcheck tests whether the stored session can still authenticate.

How it works

Remind exposes one GraphQL endpoint that can be called from the server after authentication. The browser is used to capture two values from a signed-in remind.com tab: the complete Cookie header and the x-csrf-token value. ContextMint Bridge can capture these values, or they can be supplied directly through environment variables.

After the initial capture, the server performs ordinary server-side fetches. Captured sessions are cached with file permissions set to 0600 and reused across restarts. The cache removes analytics and consent cookies, associates the session with the Remind account that authenticated it, and refreshes it from the browser after up to seven days. A session supplied through environment variables is not restored from the cache.

Call remind_list_entities first when navigating the account: its results provide the UUIDs needed by the class and chat detail tools. An expired session may appear as HTTP 200 with an Unauthorized GraphQL error, which can also indicate that the account lacks permission for an operation.

Setup and configuration

Install the package with npx -y @chrischall/remind-mcp and register it as a stdio MCP server using the npx command and package name. Authentication can be bootstrapped with the ContextMint Bridge Chrome extension and an active signed-in Remind tab. Chrome is the supported browser path described for the bridge.

Alternatively, set REMIND_COOKIE and REMIND_CSRF_TOKEN to the captured request values. REMIND_WS_PORT changes the bridge concentrator port from its default, while REMIND_SESSION_FILE changes the cached-session location. Confirmation behavior can be adjusted with MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, and MCP_CONFIRM_SECRET.

Tools and capabilities

  • remind_me returns the signed-in account.
  • remind_list_entities lists classes and chats with unread counts.
  • remind_get_classes retrieves full class information by UUID.
  • remind_list_chats lists conversation streams and their canSend permissions.
  • remind_get_messages reads messages from a chat stream.
  • remind_get_notification_settings reads preferences and delivery devices.
  • remind_set_notification_devices changes delivery-device status after confirmation.
  • remind_send_message sends to a chat or class after confirmation.
  • remind_graphql performs read-only GraphQL queries and introspection.
  • remind_healthcheck reports authentication failures by category.

When a client cannot display an interactive confirmation prompt, a write first returns a payload preview and one-time confirmation token. A repeat call with the unchanged arguments and valid token performs the write. Confirmation tokens expire according to MCP_CONFIRM_TTL_SECONDS.

Limitations and notes

The browser bootstrap is needed only when no reusable session is available, but capture completes only while the signed-in tab is making a /graphql request. The server can start without credentials, so installation-time tool discovery may succeed while the first actual call reports an authentication error.

Read-only GraphQL rejects mutations, and unknown GraphQL fields may surface as a generic internal service error. Sending messages and changing notification devices are protected writes rather than unconditional operations. The project is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Remind MCP

remind-mcp is an MCP server that connects AI clients to Remind through its GraphQL endpoint. Its main tools list classes and chats, retrieve class details and messages, inspect notification settings, send confirmed messages, run read-only GraphQL queries, and check whether the signed-in session still authenticates.

Install it with `npx -y @chrischall/remind-mcp` and register that command as a stdio MCP server in your client configuration. The package can start without credentials, but the first tool call needs a captured Remind session or the corresponding environment variables.

It authenticates with a captured `Cookie` header and `x-csrf-token` from a signed-in Remind tab. ContextMint Bridge can capture them through Chrome, or you can set `REMIND_COOKIE` and `REMIND_CSRF_TOKEN`; the server caches captured sessions for reuse.

Call `remind_send_message` after identifying the destination chat or class, and confirm the exact payload before the write proceeds. Clients with confirmation prompts can show one directly; other clients receive a preview and one-time token that must be supplied in a repeat call.

Yes, it uses the standard stdio MCP transport and can be configured in clients that support standard MCP servers, including Cursor. Authentication still requires a captured Remind session through the bridge or the relevant environment variables.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRemind MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/remind-mcp?style=directory)](https://allmcps.com/mcp/remind-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/remind-mcp"><img src="https://allmcps.com/api/badge/remind-mcp?style=directory" alt="Remind MCP on AllMCPs" /></a>