VolunteerReminder

Name: VolunteerReminder
Author: com.volunteerreminder

MCP serverMCP

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

by com.volunteerreminderrepository ↗homepage ↗v0.3.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"volunteerreminder","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability107/107 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	37 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
13 h ago	mcp initialize	ok	200	39 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
19 h ago	mcp initialize	ok	200	43 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
25 h ago	mcp initialize	ok	200	19 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
31 h ago	mcp initialize	ok	200	23 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	229 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	21 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	26 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
2 d ago	mcp initialize	ok	200	35 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools
3 d ago	mcp initialize	ok	200	52 ms	server volunteerreminder 0.3.0 · protocol 2025-06-18 · 23 tools

Tools observed via MCP handshake

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 th
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. Re
get_schedule — Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the `read` scope.
preview_schedule_occurrences — 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
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
create_schedule — Create a recurring (or custom-date) schedule and materialize its upcoming occurrences. Best practice: call preview_schedule_occurrences with the same recurrence
update_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-mater
archive_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
list_contacts — List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope.
add_contacts — 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 r
update_contact — 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.
remove_contact — 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
assign_contacts_to_schedule — 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
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 CR
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.e. where the accou
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.
get_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
set_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
remove_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 settin
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. This never reaches volunteers — it always rer
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 wit
create_account — 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
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. You never take paymen

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.volunteerreminder/mcp

first seen 1 mo ago · fetched 12 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS."
1 mo ago · declared · description → "Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS."
1 mo ago · declared · publisherName → "com.volunteerreminder"
1 mo ago · declared · homepageUrl → "https://volunteerreminder.com/docs/agents"
1 mo ago · declared · repoUrl → "https://github.com/talltimbersgroup/VolunteerReminder"
1 mo ago · declared · version → "0.3.0"
1 mo ago · declared · protocols → ["mcp"]

VolunteerReminder

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from