VolunteerReminder is an MCP server with 23 tools an agent can call, among them add_contacts, archive_schedule, assign_contacts_to_schedule. It answers at https://mcp.volunteerreminder.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 t Inputs: contacts |
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. Requ Inputs: schedule_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 Inputs: schedule_id, contact_ids |
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 Inputs: email, organization_name |
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 creat Inputs: description, job_name, group_id, schedule_type, days_of_week, nth_weekday |
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 cont |
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. Inputs: months, current_year_only |
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 |
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 |
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. Inputs: schedule_id |
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. Inputs: page, per_page |
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. Requires the `read` scope. Inputs: schedule_id, from, to, limit |
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=fa Inputs: text, confirm, preview_token, consent_attested |
list_contacts | List all volunteers on the account's roster, each with contact details and group. Requires the `read` scope. |
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. 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 concrete dates (e.g. 'the next 8 Tuesdays at 9:00 AM Central') and get their co Inputs: schedule_type, days_of_week, nth_weekday, week_of_month, day_of_month, start_month |
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. Inputs: contact_id |
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. Inputs: 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 rem Inputs: schedule_id |
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 Inputs: global_default, job_override, require_sms |
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. Fai Inputs: plan, interval |
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. Inputs: contact_id, full_name, first_name, last_name, email_address, mobile_phone |
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. This tool does NOT change the roster; use assign_con Inputs: schedule_id, description, job_name, group_id, schedule_type, days_of_week |
Every block below points at https://mcp.volunteerreminder.com/mcp. Pick your client and copy.
claude mcp add --transport http volunteerreminder https://mcp.volunteerreminder.com/mcp
{
"mcpServers": {
"volunteerreminder": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.volunteerreminder.com/mcp"]
}
}
}{
"mcpServers": {
"volunteerreminder": {
"url": "https://mcp.volunteerreminder.com/mcp"
}
}
}{
"servers": {
"volunteerreminder": {
"type": "http",
"url": "https://mcp.volunteerreminder.com/mcp"
}
}
}{
"context_servers": {
"volunteerreminder": {
"url": "https://mcp.volunteerreminder.com/mcp"
}
}
}{
"mcpServers": {
"volunteerreminder": {
"serverUrl": "https://mcp.volunteerreminder.com/mcp"
}
}
}{
"mcpServers": {
"volunteerreminder": {
"url": "https://mcp.volunteerreminder.com/mcp"
}
}
}name: VolunteerReminder
version: 0.0.1
schema: v1
mcpServers:
- name: VolunteerReminder
type: streamable-http
url: https://mcp.volunteerreminder.com/mcp{
"mcpServers": {
"volunteerreminder": {
"httpUrl": "https://mcp.volunteerreminder.com/mcp"
}
}
}{
"mcpServers": {
"volunteerreminder": {
"type": "http",
"url": "https://mcp.volunteerreminder.com/mcp"
}
}
}{
"mcpServers": {
"volunteerreminder": {
"url": "https://mcp.volunteerreminder.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.volunteerreminder.com%2Fmcp&type=streamable_http&id=volunteerreminder&name=VolunteerReminder
It answered our last check on 19 October 2026 in 323 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by volunteerreminder.com and served from mcp.volunteerreminder.com, the vendor's own domain: https://mcp.volunteerreminder.com/mcp.
23, as returned by the server's own tools/list on 11 September 2026: add_contacts, archive_schedule, assign_contacts_to_schedule, create_account, create_schedule, get_account_overview, get_open_days, get_pricing, and 15 more.
It answered our last check on 19 October 2026 in 323 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.volunteerreminder.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.volunteerreminder. Endpoint host: mcp.volunteerreminder.com. ARD identifier: urn:air:com.volunteerreminder:mcp:mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.