About vamoose
vamoose runs calendar workflows for time off, approvals, and quick actions across calendar backends. It is for people managing calendar tasks from the terminal, Claude, Slack, or a local dashboard, and supports custom JSON workflows advanced by a daemon.
Key features
- 01Runs workflows across four calendar backends
- 02Built-in time-off, notify, and away workflows
- 03Defines custom workflows in JSON
- 04Daemon advances approval and wait steps
- 05Records runs and resumes after crashes
- 06Supports HR leave filing and balance checks
Use cases
- 01Create a calendar hold and await manager approval
- 02Notify a team and file HR leave after approval
- 03Manage events across Google, Outlook, or CalDAV
- 04Define a personal away flow without approval
MCP support
vamoose provides an MCP server over stdio that exposes its commands as tools to clients. An AI agent can use it to author and run calendar workflows.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e VAMOOSE_PROVIDER -e VAMOOSE_TIMEZONE ghcr.io/dcadolph/vamoose:v0.35.0VAMOOSE_PROVIDERCalendar provider: graph, google, icloud, or caldav.VAMOOSE_TIMEZONEIANA time zone for event times, such as America/Chicago.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/dcadolph/vamoose:v0.35.0stdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.