VolunteerReminder authentication

VolunteerReminder lets an AI assistant start a free trial, import a volunteer roster, and preview upcoming shifts. New accounts start in test mode — nothing texts a real volunteer until a human turns live sends on from the dashboard.

Machine-readable metadata: /auth.md. This page is the HTML twin.

Protected resource metadata

VolunteerReminder is the authorization server. There is no separate AS host.

OAuth Allow (Claude, ChatGPT, Grok)

  1. Add the connector URL https://mcp.volunteerreminder.com (Streamable HTTP endpoint: https://mcp.volunteerreminder.com/mcp).
  2. The client reads RFC 9728, then RFC 8414, and registers at https://volunteerreminder.com/oauth/register.
  3. The coordinator signs in at https://volunteerreminder.com/oauth/authorize, then clicks Allow.
  4. The client exchanges the code at https://volunteerreminder.com/oauth/token for a vra_ access token.

No vrk_ paste on this path.

API-key bearer (Cursor-style / scripts)

  1. Start a trial at /signup or with the create_account MCP tool. That tool does not return a key.
  2. Mint a key at Account → Security.
  3. Send Authorization: Bearer vrk_… on MCP and REST v1 calls.

What VolunteerReminder does not implement

  • WorkOS agent-auth identity registration, ID-JAG, or claim ceremonies
  • A second authorization server
  • Live SMS from an agent. Import stays in test mode. A human turns live sends on from the dashboard.

Walkthrough: /docs/agents. Markdown: /auth.md.