List your agent

VolunteerReminder

MCP server● Hosted · onlinev0.3.0

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

Reviews

No review yet. Used VolunteerReminder? Be the first to help others choose.

What it does

VolunteerReminder is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.3.0
PriceNot in the registry
First seen26 Sept 2026
Last checked5d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

  • https://mcp.volunteerreminder.com/mcp streamable-http

In Claude Code: claude mcp add --transport http volunteerreminder https://mcp.volunteerreminder.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "volunteerreminder": {
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE VolunteerReminder answered an MCP connection on 14 Nov 2026 and introduced itself as volunteerreminder 0.3.2 (MCP protocol 2025-06-18).

23 tools offered to AI assistants

  • 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
  • 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.
  • 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 concrete dates (e.g. 'the next 8 Tuesdays at 9:00 AM Central') and get their co
  • 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 t
  • 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
  • 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
  • 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
  • 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 references a group_id not on this account, NOTHING is added and the error names t
  • 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. If calendar invites are on for the account, assigned volunteers may get a new, updated or cancelled c
  • 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. If calendar invites are o
Show 11 more
  • 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
  • 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
  • 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.
  • 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_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.
  • 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
  • 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.
  • send_test_reminder · Send a single TEST reminder to the account owner's own email 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;
  • 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
  • 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
  • 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

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.volunteerreminder.com/mcpDECLAREDSRC-001 Official MCP Registry5d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry5d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry5d ago
Websitehttps://volunteerreminder.com/docs/agentsDECLAREDSRC-001 Official MCP Registry5d ago
Repositoryhttps://github.com/talltimbersgroup/VolunteerReminderDECLAREDSRC-001 Official MCP Registry5d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry5d ago
Version0.3.0DECLAREDSRC-001 Official MCP Registry5d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry5d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run VolunteerReminder? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor VolunteerReminderLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of VolunteerReminder?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/volunteerreminder?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/volunteerreminder/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about VolunteerReminder

How do I connect VolunteerReminder?

Use the hosted endpoint https://mcp.volunteerreminder.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does VolunteerReminder offer?

When Electra Index connected on 14 Nov 2026, it listed 23 tools: get_account_overview, list_schedules, get_schedule, preview_schedule_occurrences, get_upcoming_shifts, create_schedule, update_schedule, archive_schedule and more. The full list is in "Live check" above.

Is VolunteerReminder online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.