Vamoose MCP server

vamoose

Calendar workflows, minus the tedium.

The moose does the paperwork. You go to the beach.

Four calendar backends behind one workflow engine that branches, approves, waits, recurs, and files real leave with your HR system, driven from your terminal, Claude, Slack, or a local dashboard, and authorable by an AI agent over MCP. Every run is recorded, and the daemon resumes exactly where it left off after a crash. Install with brew install dcadolph/tap/vamoose.

Calendar busywork is death by a thousand cuts: create the hold marked free, invite your manager, Slack them for the yes, go back in and add the team one by one, add a second blocked event so your own calendar says away, then file the leave in the HR portal. vamoose turns those chores into workflows it runs for you and advances in the background. Time off is the flagship workflow, and you can define your own.

Two minutes to running

brew install dcadolph/tap/vamoose
vamoose login --provider google   # sign in; Outlook and iCloud setup in docs
vamoose off next week --watch     # hold the dates, invite your manager
vamoose daemon                    # advances the workflow when the manager accepts
vamoose app                       # or watch and run everything from a dashboard

That is the whole flow: the hold shows as free so it blocks nobody, your manager's calendar accept is the approval, and the daemon notifies your team the moment it lands.

How it works

branch on the outcome, wait, message a channel, file the leave. Time off ships built in; author your own in a file, on the dashboard's workflow canvas, or through an AI agent.

1. Declare. A workflow is ordered steps in JSON: create a hold, gate on approval,

Microsoft Graph, Google, iCloud, or any CalDAV host. Same workflow, any backend.

1. Run. Drive it from the terminal, Claude, Slack, or vamoose app, against

invite is the approval signal (no separate approval product), timeouts and waits fire on the clock, recurring schedules re-run, and every step lands in the run history.

1. Advance. The daemon moves runs forward on its own: your manager accepting the

The built-in pto workflow is the flagship: hold shown free, manager approves by accepting, team added as optional attendees so nobody's calendar gets blocked. request, check, and promote are fronts over its steps. See Workflows.

Four backends ship behind one provider interface: Microsoft Graph (Outlook, Microsoft 365, and Teams), Google Calendar, Apple iCloud, and any standard CalDAV host. Pick one with --provider or the VAMOOSE_PROVIDER environment variable, and every command works the same across them. Approval detection is the one exception: iCloud sends invites but does not report accept/decline over CalDAV, so on iCloud you promote by hand. See providers.

Why not just calendar rules?

You can rig a version of this with one calendar's rules or a saved email. vamoose earns its keep the moment you have more than one account:

Shortened. The full README is on GitHub.