MCP server

VolunteerReminder Official

com.volunteerreminder/mcp

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.

Working at last checkVerified publisher: volunteerreminder.comAbout 9,014 tokens per request once connected23 tools

Website Source

https://mcp.volunteerreminder.com/mcp

At a glance

Type: MCP server
Publisher: volunteerreminder.com (verified by the MCP Registry)
Status: Working at last check
Tools: 23
Token cost: About 9,014 tokens per request
Sets up in: Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok
Last checked: 26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to Cursor Add to VS Code VS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http volunteerreminder https://mcp.volunteerreminder.com/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

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

Gemini CLI

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

Cursor

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

VS Code

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

Antigravity

agy mcp add volunteerreminder https://mcp.volunteerreminder.com/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"volunteerreminder","server_url":"https://mcp.volunteerreminder.com/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"volunteerreminder","server_url":"https://mcp.volunteerreminder.com/mcp"}

Tools

add_contacts ~721 tokens
Add one or more volunteers to the roster in a single call. ALL-OR-NOTHING: if the batch would push the account past its plan's volunteer limit, or any contact references a group_id not on this account, NOTHING is added and the error names the limit/count/bad id so you can adjust. Phone numbers are v
archive_schedule ~174 tokens
Archive (soft-delete) a schedule. It stops appearing in the active list and no further reminders go out for it, but past reminder history is preserved. This is reversible only from the dashboard. Confirm with the user before archiving. Requires the `schedules:write` scope.
assign_contacts_to_schedule ~265 tokens
Assign volunteers to a schedule. This REPLACES the schedule's entire roster — send the COMPLETE desired set of contact ids, not a delta (pass an empty array to clear it). Every id must belong to this account or the whole request is rejected with the offending ids named. Does not change occurrences.
create_account Changes accounts · ~431 tokens
Start a new VolunteerReminder account for a human, using their email address. This does NOT finish signup and does NOT return an API key: it emails the person a verification link they must click to activate the account. Nothing can be built on the account and no reminders can ever send until they ve
create_schedule ~1257 tokens
Create a recurring (or custom-date) schedule and materialize its upcoming occurrences. Best practice: call preview_schedule_occurrences with the same recurrence settings first and confirm the dates with the user. This tool returns the created schedule AND an inline preview of its next occurrences so
get_account_overview ~190 tokens
Read the current VolunteerReminder account: organization name, plan and entitlements, current reminder send mode, and volunteer usage vs the plan limit. Call this first to understand what the account can do before creating schedules or contacts. Note the `reminder_mode`: an account created through t
get_open_days ~185 tokens
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.e. where the account still needs volunteers. Requires the `read` scope.
get_pricing ~128 tokens
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). No API key required — use this to help a user comparison-shop or decide which plan fits before they s
get_reminder_settings ~114 tokens
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. Reminder overrides are per JOB, not per individual schedule. Requires the `read` scope.
get_schedule ~138 tokens
Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.
get_send_history ~156 tokens
Read recent reminder outcomes — which reminders were sent and which failed — newest first, paginated. Use this to confirm reminders actually went out. Requires the `read` scope.
get_upcoming_shifts ~317 tokens
Who is volunteering when. Lists upcoming shifts with date/time, schedule, whether that date is still on, and the rostered volunteers' names. Omit `schedule_id` to cover EVERY active schedule in one call (best for questions like "who is on this Sunday?": pass from and to as that same date). A bare "y
import_volunteer_schedule ~561 tokens
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. Always call first with confirm=false and show the user the upcoming shifts; only call again w
list_contacts ~72 tokens
List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.
list_schedules ~99 tokens
List all active (non-archived) schedules on the account, each with its description, job/role (name and job_id), next upcoming occurrence, and how many volunteers are rostered. Requires the `read` scope.
preview_schedule_occurrences ~982 tokens
PURE and side-effect-free: computes the next occurrence dates a recurrence configuration WOULD produce, without creating anything. Use this to show the user the concrete dates (e.g. 'the next 8 Tuesdays at 9:00 AM Central') and get their confirmation BEFORE calling create_schedule. Requires the `rea
remove_contact ~150 tokens
Remove (soft-delete) a volunteer from the roster. This frees a volunteer-cap slot and removes them from any schedule rosters they were on. Confirm with the user before removing. Requires the `contacts:write` scope.
remove_reminder_rule ~149 tokens
Remove a reminder lead-time rule. Provide `job_id` to remove that job's override; omit it to clear the account-wide default. Returns the updated reminder settings. Requires the `reminders:write` scope.
send_test_reminder Sends messages · ~205 tokens
Send a single TEST reminder to the account owner's own email/phone so they can preview what a reminder looks like. This never reaches volunteers — it always reroutes to the owner. Optionally pass a schedule_id to preview that schedule's reminder; otherwise a generic sample is sent. It is a real mess
set_reminder_rule ~628 tokens
Set the reminder lead time: the account-wide default and/or a per-job override. Provide at least one of `global_default` or `job_override`, and set at least one of days/hours/minutes greater than zero. Overrides are per JOB (a job may back several schedules); get the job_id from list_schedules. Repl
start_checkout Moves money · ~224 tokens
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. You never take payment yourself and never see card details. Use get_pricing first to pick a plan. Fails if the account already has an active subscription (manage
update_contact ~568 tokens
Update a volunteer's details. Send only the fields you want to change; a field set to null clears it. Requires the `contacts:write` scope.
update_schedule ~1300 tokens
Partially update a schedule — send only the fields you want to change; unset fields keep their current value. Changing recurrence fields recomputes and re-materializes future occurrences. If the change would remove upcoming shifts, nothing is saved and the tool returns confirm_remove_required with t

Browse

Related MCP servers

Deputy MCP by usefulapi
See rosters, timesheets, leave and staff in Deputy, and create shifts, leave and memos.
Shiftbase MCP by usefulapi
Read Shiftbase rosters, timesheets, absences and availability; schedule shifts and review absences.
Shift Scheduler
Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness.
Elvanto MCP by usefulapi
Look up people, groups, service rosters, songs, follow-up flows and giving in Elvanto.
I'm In! Sign-up Sheets
Turn an email, notes or a flyer into a free sign-up sheet with reminders and waitlists.
Source Library
Search 15K rare pre-modern texts translated to English: philosophy, religion, science, literature.
Apply2Volunteer
Preview or grade a volunteer form. No API key. Free sign-up to publish.
Moltline Optimize
Vehicle routing, 3-D packing, cutting stock, rostering and knapsack with OR-Tools. 7 of 11 free.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/com.volunteerreminder/mcp.svg)](https://aptlynx.net/servers/com.volunteerreminder/mcp)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents