com.volunteerreminder/mcp

up checked 2026-11-10T23:37:19.141Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

VolunteerReminder

Publisher-provided description

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

Summary by lookupd

Imports volunteer rosters, manages schedules and reminders; SMS stays in test mode until a human enables live sending.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add mcp --url https://mcp.volunteerreminder.com/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (23 tools)

Publisher-provided text

• 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
• 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
• 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
• 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`
• create_schedule Create a recurring (or custom-date) schedule and materialize its upcoming occurrences. Best practice: call preview_schedule_occurrences with the same recurrence
• 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
• 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
• 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 r
• 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 a
• 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
• 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
• 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
• 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_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_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
• 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
• 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 so they can preview what a reminder looks like. This never reaches volunteers — it always reroutes
• 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
• 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
• 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

Details

• Version: 0.3.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 746 ms
• First indexed: 2026-11-01T08:59:58.697Z
• Last seen in registry: 2026-11-01T08:59:58.697Z
• Repository: https://github.com/talltimbersgroup/VolunteerReminder
• Website: https://volunteerreminder.com/docs/agents

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/com.volunteerreminder/mcp.svg)](https://lookupd.com/servers/com.volunteerreminder/mcp)

• 62071 servers
• Last crawl: 2026-11-11T16:17:25.167Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp