VolunteerReminder
Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.
| Endpoint | https://mcp.volunteerreminder.com/mcp (streamable-http) |
|---|---|
| Registry version | 0.3.0 |
| Now | 23 tools · grade C (67) · pin ts_495e76662e5bf582425cdd88e1388cf2 · protocol 2025-06-18 |
| First / last listed | 2026-10-28 00:22 UTC / 2026-10-28 00:22 UTC |
| Grade over time | 2026-10-28: C (67), 23 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: get_account_overview list_schedules get_schedule preview_schedule_occurrences get_upcoming_shifts create_schedule update_schedule archive_schedule list_contacts add_contacts update_contact remove_contact assign_contacts_to_schedule import_volunteer_schedule get_open_days get_reminder_settings get_send_history set_reminder_rule remove_reminder_rule send_test_reminder get_pricing create_account start_checkout
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 params: none |
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. params: none |
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. params: schedule_id* |
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 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. params: schedule_type*, days_of_week, nth_weekday, week_of_month, day_of_month, start_month, time, start_date, end_date, custom_dates, count |
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. params: schedule_id, from, to, limit |
create_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. Requ params: description*, job_name*, group_id, schedule_type*, days_of_week, nth_weekday, week_of_month, day_of_month, start_month, time, start_date, end_date, custom_dates, contact_ids, notes |
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-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 params: schedule_id*, description, job_name, group_id, schedule_type, days_of_week, nth_weekday, week_of_month, day_of_month, start_month, time, start_date, end_date, custom_dates, notes, confirm_remove, confirm_token |
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 reversible only from the dashboard. Confirm with the user before archiving. Requires the `schedules:write` scope. params: schedule_id* |
list_contacts | List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope. params: none |
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 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 t params: contacts*, consent_attested |
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. params: contact_id*, full_name, first_name, last_name, email_address, mobile_phone, land_phone, group_id, notes, consent_attested |
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 before removing. Requires the `contacts:write` scope. params: contact_id* |
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 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. params: schedule_id*, contact_ids* |
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. 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-m params: text*, confirm, preview_token, consent_attested |
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 account still needs volunteers. Requires the `read` scope. params: months, current_year_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. Reminder overrides are per JOB, not per individual schedule. Requires the `read` scope. params: none |
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 the `read` scope. params: page, per_page |
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 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. params: global_default, job_override, require_sms |
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 settings. Requires the `reminders:write` scope. params: job_id |
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 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. params: schedule_id |
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). No API key required — use this to help a user comparison-shop or decide which plan fits before they sign up. params: none |
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 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 params: email*, organization_name |
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 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`). params: plan*, interval |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.