# Volunteerreminder MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.volunteerreminder%2Fmcp
Registry id: `mcp-registry/com.volunteerreminder/mcp`
Status: live (checked 2026-10-27T08:06:40.231Z)

## Verdict

Volunteerreminder MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 671 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 23 tools, costing an agent about 8,543 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 671 ms | 33% of MCP servers |
| p95 handshake latency | 3027 ms | — |
| Checks in 30 days | 5,025 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 23 | — |
| Tool-list size for an agent | ~8,543 tokens | 33% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "volunteerreminder-mcp-server": {
      "type": "http",
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}
```

Claude Code:

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

## Tools (23)

- `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
- `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 
- `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 
- `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
- `create_schedule`: Create a recurring (or custom-date) schedule and materialize its upcoming occurrences. Best practice: call preview_schedule_occurrences with the same recurrence
- `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
- `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_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
- `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_schedule`: 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`: Read recent reminder outcomes — which reminders were sent and which failed — newest first, paginated. Use this to confirm reminders actually went out. Requires 
- `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` 
- `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
- `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 (name and job_id), next upcoming occurrence, and how many volunteer
- `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
- `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
- `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
- `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
- `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
- `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.
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.