Productivity

volunteerreminder.com

Manage volunteer schedules and reminders, including viewing account details, schedules, and upcoming shifts.

1 endpoint23 known toolsFirst detected September 8, 2026Last detected September 8, 2026

ENDPOINT 1

https://mcp.volunteerreminder.com/mcp

No auth detected

MCP server metadata

Name: volunteerreminder
Version: 0.3.0

Capabilities

tools.listChanged

Server instructions

VolunteerReminder sets up and sends automated shift reminders (email + SMS) to an organization's volunteers. Auth: every tool except get_pricing and create_account needs the connected account. Claude / ChatGPT / Grok connectors use VolunteerReminder's OAuth Allow screen (no vrk_ paste). Cursor-style clients may pass `Authorization: Bearer vrk_…`. If a tool reports missing auth, use create_account to start signup, then have the human complete Allow or mint a key from the dashboard. Safety model: an account created through this connector (create_account) starts in `test` reminder mode — reminders reroute to the account owner's own address, never real volunteers. Only a human can switch it to `live` from the dashboard. You cannot delete an account, change its login email, change billing, or flip reminder mode to live through these tools. Recommended flow: create_account (human verifies email) → complete VolunteerReminder's OAuth Allow screen (or paste a vrk_ key from Account → Security) → import_volunteer_schedule with confirm=false (show the preview) → import_volunteer_schedule with confirm=true → get_upcoming_shifts. Alternatively, build piece by piece: get_account_overview → preview_schedule_occurrences → create_schedule → add_contacts → assign_contacts_to_schedule → set_reminder_rule. Use send_test_reminder to let the owner preview a reminder before going live. Never flip reminder mode to live, and never enable the confirm loop or substitute finder.

Known tools 23

get_account_overview

Read the current VolunteerReminder account: organization name, plan and entitlements, current reminder send mode, and volunteer usage vs the plan limit.

Potential side effects

list_schedules

List all active (non-archived) schedules on the account, each with its description, job/role, next upcoming occurrence, and how many volunteers are rostered.

Inferred read-only

get_schedule

Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes.

Inferred read-only

preview_schedule_occurrences

PURE and side-effect-free: computes the next occurrence dates a recurrence configuration WOULD produce, without creating anything.

Inferred read-only

get_upcoming_shifts

List a schedule's upcoming occurrences (shifts) in a date range, each with its date/time, whether the roster is attending that date, and the assigned volunteers.

Inferred read-only

create_schedule

Create a recurring (or custom-date) schedule and materialize its upcoming occurrences.

Potential side effects

update_schedule

Partially update a schedule — send only the fields you want to change; unset fields keep their current value.

Potential side effects

archive_schedule

Archive (soft-delete) a schedule.

Potential side effects

list_contacts

List all volunteers on the account's roster, each with contact details and group.

Inferred read-only

add_contacts

Add one or more volunteers to the roster in a single call.

Inferred read-only

update_contact

Update a volunteer's details.

Potential side effects

remove_contact

Remove (soft-delete) a volunteer from the roster.

Potential side effects

assign_contacts_to_schedule

Assign volunteers to a schedule.

Inferred read-only

import_volunteer_schedule

Parse a pasted or uploaded volunteer roster + schedule (CSV or a table with columns like name, phone, email, job/role, day, start, end) and either PREVIEW or CREATE the contacts, schedules, and assignments.

Potential side effects

get_open_days

List calendar days in the look-ahead window that have no attendable shift yet, plus recurring monthly slots not yet claimed by a schedule — i.

Inferred read-only

get_reminder_settings

Read the account's reminder lead times (the account-wide default plus any per-job overrides) and which channels (email / SMS) are available on the current plan.

Potential side effects

get_send_history

Read recent reminder outcomes — which reminders were sent and which failed — newest first, paginated.

Inferred read-only

set_reminder_rule

Set the reminder lead time: the account-wide default and/or a per-job override.

Inferred read-only

remove_reminder_rule

Remove a reminder lead-time rule.

Potential side effects

send_test_reminder

Send a single TEST reminder to the account owner's own email/phone so they can preview what a reminder looks like.

Potential side effects

get_pricing

Read VolunteerReminder's public plan catalog: each plan's monthly and annual price (USD), volunteer limit, and included features (SMS reminders are included with no per-message credits or metering).

Potential side effects

create_account

Start a new VolunteerReminder account for a human, using their email address.

Potential side effects

start_checkout

Get a Stripe-hosted Checkout URL for the account to subscribe to a paid plan, then HAND THE URL TO THE HUMAN to open and complete payment.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.volunteerreminder]
url = "https://mcp.volunteerreminder.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "volunteerreminder": {
      "type": "http",
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: volunteerreminder
Remote MCP URL: https://mcp.volunteerreminder.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "volunteerreminder": {
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "volunteerreminder": {
      "type": "http",
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "volunteerreminder",
  "transport": "streamable-http",
  "url": "https://mcp.volunteerreminder.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.