A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
VolunteerReminder is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
23
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Import a volunteer roster and preview shifts. Test-mode until a human enables live SMS.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http volunteerreminder-mcp https://mcp.volunteerreminder.com/mcp
# 2 — ask your agent for something these tools do
# get_account_overview, list_schedules, get_schedule and 20 more
VolunteerReminder costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VOAll 1 server
volunteerreminder1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http volunteerreminder-mcp https://mcp.volunteerreminder.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
No parameter schema on file.
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.
No parameter schema on file.
Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes. Requires the read scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | integer | yes | The schedule's numeric id (from list_schedules or get_schedule). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_type | string | yes | Recurrence shape. 'weekly' recurs on one or more days of the week; 'biweekly' is the same weekday mask every 14 days (start_date picks which week; not BiMonthly, which is every other month); 'monthly_ |
| days_of_week | array | no | Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly' or 'biweekly'; ignored otherwise. |
| nth_weekday | string | no | The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types. |
| week_of_month | integer | no | Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1. |
| day_of_month | integer | no | Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th). |
| start_month | integer | no | Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month. |
| time | no | Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time. | |
| start_date | no | "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound. For 'biweekly' this also picks which week the 14-day rotation lands on; when omitted, the server us | |
| end_date | no | "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date. | |
| custom_dates | array | no | Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise. |
| count | integer | no | How many upcoming occurrences to return (default 8, max 52). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | integer | no | Limit to one schedule (id from list_schedules). Omit to include all active schedules. |
| from | string | no | Start of the range: "yyyy-MM-dd" (account timezone) or a full ISO 8601 datetime. Defaults to now. |
| to | string | no | End of the range, same formats as from; a bare date includes that whole day. Defaults to 90 days from now. |
| limit | integer | no | Maximum shifts to return (default 20, max 100). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | Short label shown on the schedule list and in reminders, e.g. "Sunday greeters". |
| job_name | string | yes | The role/task volunteers are reminded about. Matched case-insensitively against the account's existing jobs and created if new. |
| group_id | no | Id of an existing volunteer group to attach, or null. Unknown ids are ignored. | |
| schedule_type | string | yes | Recurrence shape. 'weekly' recurs on one or more days of the week; 'biweekly' is the same weekday mask every 14 days (start_date picks which week; not BiMonthly, which is every other month); 'monthly_ |
| days_of_week | array | no | Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly' or 'biweekly'; ignored otherwise. |
| nth_weekday | string | no | The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types. |
| week_of_month | integer | no | Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1. |
| day_of_month | integer | no | Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th). |
| start_month | integer | no | Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month. |
| time | no | Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time. | |
| start_date | no | "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound. For 'biweekly' this also picks which week the 14-day rotation lands on; when omitted, the server us | |
| end_date | no | "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date. | |
| custom_dates | array | no | Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise. |
| contact_ids | array | no | Optional initial roster (volunteer contact ids) to assign at creation. Ids not owned by this account are silently dropped. To change a roster later, use assign_contacts_to_schedule. |
| notes | no | Free-text internal notes, or null. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | integer | yes | The schedule's numeric id (from list_schedules or get_schedule). |
| description | string | no | New schedule label. |
| job_name | string | no | New job/role name. |
| group_id | no | New group id, or null to detach. Unknown ids are ignored. | |
| schedule_type | string | no | Recurrence shape. 'weekly' recurs on one or more days of the week; 'biweekly' is the same weekday mask every 14 days (start_date picks which week; not BiMonthly, which is every other month); 'monthly_ |
| days_of_week | array | no | Weekday names this recurs on, e.g. ["tuesday","thursday"]. Required (non-empty) when schedule_type is 'weekly' or 'biweekly'; ignored otherwise. |
| nth_weekday | string | no | The weekday that recurs, for schedule_type 'monthly_nth'/'bimonthly_nth'. Defaults to sunday for those types. |
| week_of_month | integer | no | Which occurrence of the weekday in the month (1st–5th), for the Nth-weekday types. Defaults to 1. |
| day_of_month | integer | no | Fixed day of the month for the 'fixed' types. Defaults to 1. Clamped to the last day of shorter months (e.g. 31 in February becomes the 28th/29th). |
| start_month | integer | no | Anchor month (1=January … 12=December) the every-other-month cadence steps from, for the 'bimonthly_*' types. Defaults to the account's current month. |
| time | no | Wall-clock time of day "HH:mm" (24-hour) in the account timezone, or null for no specific time. | |
| start_date | no | "yyyy-MM-dd" (account timezone) before which no occurrences materialize, or null for no lower bound. For 'biweekly' this also picks which week the 14-day rotation lands on; when omitted, the server us | |
| end_date | no | "yyyy-MM-dd" (account timezone) after which occurrences stop, or null for no end date. | |
| custom_dates | array | no | Explicit list of "yyyy-MM-dd" dates. Required (non-empty) when schedule_type is 'custom'; ignored otherwise. |
| notes | no | New notes, or null to clear. | |
| confirm_remove | boolean | no | Set true to apply a change that removes upcoming shifts, only after the user approved the dates a previous confirm_remove_required result listed. Requires confirm_token from that result. |
| confirm_token | string | no | The confirm_token from the confirm_remove_required result for this same change. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | integer | yes | The schedule's numeric id (from list_schedules or get_schedule). |
List all volunteers on the account's roster, each with contact details and group. Requires the read scope.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contacts | array | yes | The volunteers to add (1–200 per call). Each needs at least a full_name. |
| consent_attested | boolean | no | Required true when any volunteer here has a mobile_phone. Set it only after the user confirms these volunteers agreed to receive shift-reminder texts. Not needed for email-only volunteers. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | The contact's numeric id (from list_contacts). |
| full_name | string | no | New display name. |
| first_name | no | First name, or null. | |
| last_name | no | Last name, or null. | |
| email_address | no | Email address reminders may be sent to, or null. | |
| mobile_phone | no | Mobile number for SMS reminders. Accepts E.164 (+15125550100) or a plain 10-digit US/Canada number; stored as E.164. Send null to clear. | |
| land_phone | no | Landline number (informational only, never texted), or null. | |
| group_id | no | Id of an existing group on this account to file the contact under, or null. | |
| notes | no | Free-text notes about the contact, or null. | |
| consent_attested | boolean | no | Required true when setting or changing mobile_phone. Set it only after the user confirms these volunteers agreed to receive shift-reminder texts. Not needed for email-only volunteers. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | The contact's numeric id (from list_contacts). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | integer | yes | The schedule to assign the roster to. |
| contact_ids | array | yes | The complete set of volunteer contact ids for this schedule (replaces any existing roster). Empty array clears the roster. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The roster as CSV, TSV, pipe-delimited text, or a headerless table in the order name, phone, email, job, day, start, end. Quoted CSV fields are fine. Do not log this text. |
| confirm | boolean | no | false (default) = parse and preview only, no writes. true = create the contacts, schedules, and assignments after the user approved the preview. confirm=true requires preview_token from the preceding |
| preview_token | string | no | Required when confirm=true. Copy the preview_token returned by the preceding confirm=false call for this exact roster text. |
| consent_attested | boolean | no | Required true on confirm=true when any contact has a phone number. Affirms the volunteers agreed to receive shift-reminder texts. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| months | integer | no | How many months to look ahead (1–24). Default 12. |
| current_year_only | boolean | no | When true (the default), clamp the window to the end of the current calendar year instead of crossing into next year. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-indexed page number. Default 1. |
| per_page | integer | no | Rows per page (max 100). Default 20. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| global_default | object | no | Set (or replace) the account-wide default lead time. |
| job_override | object | no | Create or replace the lead-time override for one job. |
| require_sms | boolean | no | Assert SMS should be used. If true and the plan does NOT include SMS, the whole request is rejected with a message that the plan does not include SMS (nothing is saved). Omit or set false to make no a |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | integer | no | Remove this job's lead-time override. Omit to clear the account-wide default. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | integer | no | Preview the reminder for this schedule. Omit for a generic sample reminder. |
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.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The account owner's email address. The verification / sign-in link is sent here; only the person who controls this inbox can activate the account. Required. | |
| organization_name | string | no | Display name for the organization (becomes the account name). Optional — defaults to a placeholder the owner can rename after verifying. The account timezone defaults to America/Chicago and is editabl |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | yes | The plan id to subscribe to (see get_pricing). |
| interval | string | no | Billing interval. Defaults to monthly. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install VolunteerReminder or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish VolunteerReminder can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.