RotaHog is now in the Claude directory

Published on: September 28, 2026, by: João Alves

When we launched the MCP server, connecting it still asked something of you. You had to find our URL, paste it into a settings screen, and in some clients create an API token first and keep it somewhere safe. Not hard, but enough friction that plenty of people never got round to it.

That step is gone. RotaHog is now listed in the Claude connector directory, so you can add it from inside Claude without touching a config file or creating a token.

How to add it

1. Open Claude and go to Settings, then Connectors.
2. Click Browse connectors and search for RotaHog. Or skip straight to the listing: claude.ai/directory/rotahog-com.
3. Click Connect. Claude sends you to RotaHog to sign in, shows you what it is asking for, and you approve it.

That is the whole setup. No URL to copy, no token to rotate, nothing to keep safe. Claude and RotaHog do the handshake between themselves using OAuth, the same standard your bank uses when you connect an accounting app.

What you can ask for

Once connected, your rotations are a question away:

• "Set up a weekday standup rotation for Alice, Bruno and Carla, starting Monday"
• "Who's on call this week?"
• "Show me the schedule for our newsletter rotation for the next two months"
• "Mark today's deploy captain turn as complete"
• "Find a substitute for my turn next week, I'm on holiday"

Behind those questions are eight tools: list your rotations, get a rotation's details, list turns with filters, get who is currently on duty, create a rotation with a year of schedule, complete a turn, substitute a turn, and cancel a turn. Creating a rotation by describing it out loud is the one that surprises people most, so try that first.

What Claude can and cannot see

The consent screen asks for reading your rotations, writing to them, or both, and it names the client before anything is connected. Claude sees the rotations you own or take part in, and nothing else in your account.

Every connected client is listed on your API tokens page, and you can disconnect any of them from there. Disconnecting takes effect immediately.

Paid features stay paid. substitute_turn needs a plan with Find a substitute and cancel_turn needs one with Cancel a turn, exactly as in the web app. On a plan without them, the tool says so rather than failing quietly.

It is free

The MCP server is on every plan, including free. An assistant can only do what you can already do in the browser, within the same limits, so charging for the doorway would have been charging for a wall that is not there.

Not using Claude?

Nothing changed for you. The connector URL still works in ChatGPT, Cursor, Claude Code, and any other client that speaks remote MCP, with OAuth where the client supports it and an API token where it does not. The MCP docs have the setup for each.