io.github.dcadolph/vamoose
Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
ghcr.io/dcadolph/vamoose:v0.35.0claude mcp add vamoose -e 'VAMOOSE_PROVIDER=<VAMOOSE_PROVIDER>' -e 'VAMOOSE_TIMEZONE=<VAMOOSE_TIMEZONE>' -- docker run -i --rm ghcr.io/dcadolph/vamoose:v0.35.0 mcp
{
"mcpServers": {
"vamoose": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/dcadolph/vamoose:v0.35.0",
"mcp"
],
"env": {
"VAMOOSE_PROVIDER": "<VAMOOSE_PROVIDER>",
"VAMOOSE_TIMEZONE": "<VAMOOSE_TIMEZONE>"
}
}
}
}
Environment variables
VAMOOSE_PROVIDERCalendar provider: graph, google, icloud, or caldav.VAMOOSE_TIMEZONEIANA time zone for event times, such as America/Chicago.
Frequently asked questions
What is io.github.dcadolph/vamoose?
Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
How do I install io.github.dcadolph/vamoose?
It runs on your machine. In Claude Code: claude mcp add vamoose -e 'VAMOOSE_PROVIDER=<VAMOOSE_PROVIDER>' -e 'VAMOOSE_TIMEZONE=<VAMOOSE_TIMEZONE>' -- docker run -i --rm ghcr.io/dcadolph/vamoose:v0.35.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.dcadolph/vamoose need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.dcadolph/vamoose open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.dcadolph/vamoose?
It is published by dcadolph. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.