
Vamoose
io.github.dcadolphPublished by GitHub account dcadolphv0.35.0Updated Oct 24, 2026
Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
Overview
Vamoose is a local calendar workflow engine that lets an assistant book time off, create holds and events, and advance approval workflows across Google, Outlook
- What you can do
- Create holds, out-of-office blocks and plain events on a connected calendar, optionally inviting attendees or a manager for approval. Run built-in or custom workflows such as time off, notify-only and away, and advance them when the manager accepts. Check approval status, promote an approved hold to the team as optional attendees, or cancel a hold and notify everyone. Look up coverage for a date range and read remaining leave balance when an HR system is configured. Review run history and define workflows as JSON files.
- When to use it
- Useful when you want an assistant to handle recurring calendar busywork such as requesting time off, blocking out-of-office time, or running a multi-step approval flow, especially across more than one calendar account. Best for people whose calendar backend is Microsoft Graph, Google, iCloud or CalDAV.
- Requirements
- Runs as a local process (Homebrew, Scoop, Docker or Go install) and is started as the vamoose binary with the mcp argument. Authenticate once first so a cached token exists. One calendar backend must be configured via VAMOOSE_PROVIDER, with provider credentials such as VAMOOSE_CLIENT_ID and VAMOOSE_TENANT, VAMOOSE_GOOGLE_CLIENT_ID and VAMOOSE_GOOGLE_CLIENT_SECRET, or VAMOOSE_ICLOUD_USERNAME and VAMOOSE_ICLOUD_APP_PASSWORD. HR balance and leave filing need BambooHR or webhook settings. VAMOOSE_GO
Installation
In SourceWeft
- Open Vamoose in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.35.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.