VolunteerReminder

com.volunteerreminderPublished by volunteerreminder.comOfficial publisherv0.3.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server for VolunteerReminder that lets an assistant manage volunteer rosters, recurring schedules, and reminder settings for an organization.

What you can do
Read account overview, plan entitlements, reminder settings, send history and public pricing, and create accounts or start Stripe checkout for a plan (handing the URL to the human). Manage schedules: list, get, preview occurrences, create, update and archive recurring or custom-date schedules. Manage volunteers: list, add, update and remove contacts, and replace a schedule's roster. Import a pasted or uploaded roster and schedule from CSV or a table, with a preview step before creating anything. Check upcoming shifts, open days needing volunteers, and send a test reminder to the account owner.
When to use it
Useful for volunteer coordinators or organizations already on VolunteerReminder who want an assistant to set up recurring schedules, import rosters, answer who-is-on-when questions, and adjust reminder lead times without using the dashboard.
Requirements
A remote streamable HTTP endpoint; no local package. An existing VolunteerReminder account with API access and scopes such as read, schedules:write, contacts:write and reminders:write. Some tools, such as get_pricing, need no API key. Network access to the service.
Before you install
Write tools create, update, archive and remove schedules and contacts, and assign_contacts_to_schedule replaces the entire roster, so confirm with the user first. send_test_reminder sends a real message, though rerouted to the owner. start_checkout leads to a paid Stripe subscription; the assistant never takes payment. Import can create contacts and schedules in bulk; preview first. Volunteer names, phone numbers and emails are sent to the service.

Installation

In SourceWeft

  1. Open VolunteerReminder in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.volunteerreminder%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

23

get_account_overview

Get account overview

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 this connector (create_account) starts in `test` (reminders reroute to the owner, never to volunteers); only a human can switch it to `live` from the dashboard. `effective_mode` is what actually happens at send time.

Takes no parameters.

list_schedules

List schedules

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.

Takes no parameters.

get_schedule

Get a schedule

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

Parametersschedule_idrequired

preview_schedule_occurrences

Preview upcoming occurrence dates

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 `read` scope.

Parameterstimecountend_datestart_datenth_weekdaystart_monthcustom_datesday_of_monthdays_of_weekschedule_typerequiredweek_of_month

get_upcoming_shifts

Get upcoming shifts

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 "yyyy-MM-dd" `to` includes that whole day. Requires the `read` scope.

Parameterstofromlimitschedule_id

create_schedule

Create a schedule

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 you can show what was set up. You can optionally seed the roster with contact_ids at creation. Requires the `schedules:write` scope.

Parameterstimenotesend_dategroup_idjob_namerequiredstart_datecontact_idsdescriptionrequirednth_weekdaystart_monthcustom_datesday_of_month+3 more

update_schedule

Update a schedule

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 the `removed` dates and a `confirm_token`. Show the user those dates; only if they agree, call again with the same changes plus confirm_remove: true and that confirm_token. This tool does NOT change the roster; use assign_contacts_to_schedule for that. Requires the `schedules:write` scope.

Parameterstimenotesend_dategroup_idjob_namestart_datedescriptionnth_weekdayschedule_idrequiredstart_monthcustom_datesday_of_month+5 more

archive_schedule

Archive a schedule

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.

Parametersschedule_idrequired

list_contacts

List volunteers

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

Takes no parameters.

add_contacts

Add volunteers

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 validated and normalized to E.164. Adding a mobile number needs consent_attested=true (ask the user to confirm the volunteers agreed to texts). To put new volunteers on a shift, follow with assign_contacts_to_schedule. Requires the `contacts:write` scope.

Parameterscontactsrequiredconsent_attested

update_contact

Update a volunteer

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.

Parametersnotesgroup_idfull_namelast_namecontact_idrequiredfirst_nameland_phonemobile_phoneemail_addressconsent_attested

remove_contact

Remove a volunteer

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.

Parameterscontact_idrequired

assign_contacts_to_schedule

Set a schedule's roster

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. Requires the `contacts:write` scope.

Parameterscontact_idsrequiredschedule_idrequired

import_volunteer_schedule

Import a volunteer roster and 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. Always call first with confirm=false and show the user the upcoming shifts; only call again with confirm=true, passing back preview_token from that preview, after they approve. Import is test-mode only and is refused on some accounts. Use create_account first if they do not have an account — do not invent a second signup path. This tool never changes reminder mode, never enables the confirm loop or substitute finder, and never texts real volunteers. New accounts stay in test mode. Requires `read` for preview; `schedules:write` and `contacts:write` to commit. Set consent_attested=true on commit when any row has a phone number (the coordinator affirms the volunteers agreed to be texted).

Parameterstextrequiredconfirmpreview_tokenconsent_attested

get_open_days

Get open days (who do we still need?)

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.

Parametersmonthscurrent_year_only

get_reminder_settings

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. Reminder overrides are per JOB, not per individual schedule. Requires the `read` scope.

Takes no parameters.

get_send_history

Get reminder send history

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.

Parameterspageper_page

set_reminder_rule

Set a reminder rule

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. Replaces any earlier override for that job. Requires the `reminders:write` scope.

Parametersrequire_smsjob_overrideglobal_default

remove_reminder_rule

Remove a reminder rule

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.

Parametersjob_id

send_test_reminder

Send a test reminder to the account owner

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 message that cannot be unsent, so confirm with the user first. Requires the `reminders:write` scope.

Parametersschedule_id

get_pricing

Get pricing and plans

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 sign up.

Takes no parameters.

create_account

Create an account (pending email verification)

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 verify — and even then a new account starts in safe `test` mode (reminders reach only the owner, never volunteers) until a human turns on live sending from the dashboard. Idempotent: calling it again with the same email re-sends the link and creates no duplicate. After the user tells you they've verified, they mint an API key from the dashboard and reconnect this connector with it. Tell the user to check their email.

Parametersemailrequiredorganization_name

start_checkout

Get a Stripe Checkout link to subscribe

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 that from the billing dashboard). Requires a connected API key (any scope with `read`).

Parametersplanrequiredinterval

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.