INDIVIDUAL MCP TOOL

assign_contacts_to_schedule

Assign volunteers to a schedule.

volunteerreminder.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.volunteerreminder.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for assign_contacts_to_schedule and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.volunteerreminder]
url = "https://mcp.volunteerreminder.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: volunteerreminder
Remote MCP URL: https://mcp.volunteerreminder.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "volunteerreminder": {
      "type": "http",
      "url": "https://mcp.volunteerreminder.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "volunteerreminder",
  "transport": "streamable-http",
  "url": "https://mcp.volunteerreminder.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

get_account_overview — Read the current VolunteerReminder account: organization name, plan and entitlements, current reminder send mode, and volunteer usage vs the plan limit.
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.
get_schedule — Get one schedule's full configuration: recurrence settings, job/role, group, roster (contact ids), start/end dates, and notes.
preview_schedule_occurrences — PURE and side-effect-free: computes the next occurrence dates a recurrence configuration WOULD produce, without creating anything.
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.
create_schedule — Create a recurring (or custom-date) schedule and materialize its upcoming occurrences.
update_schedule — Partially update a schedule — send only the fields you want to change; unset fields keep their current value.
archive_schedule — Archive (soft-delete) a schedule.