Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
Most planning and project tracking work still happens through a UI a human drives. Vamoose MCP server moves it into the conversation instead. Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
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.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: VAMOOSE_CLIENT_ID, VAMOOSE_TENANT, VAMOOSE_TIMEZONE, VAMOOSE_PROVIDER, VAMOOSE_ICLOUD_USERNAME, VAMOOSE_ICLOUD_APP_PASSWORD, VAMOOSE_CALDAV_URL, VAMOOSE_CALDAV_USERNAME. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by dcadolph; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
{
"mcpServers": {
"vamoose": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/dcadolph/vamoose"],
"env": {
"VAMOOSE_CLIENT_ID": "your-value",
"VAMOOSE_TENANT": "your-value",
"VAMOOSE_TIMEZONE": "your-value",
"VAMOOSE_PROVIDER": "your-value",
"VAMOOSE_ICLOUD_USERNAME": "your-value",
"VAMOOSE_ICLOUD_APP_PASSWORD": "your-value",
"VAMOOSE_CALDAV_URL": "your-value",
"VAMOOSE_CALDAV_USERNAME": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| VAMOOSE_CLIENT_ID | Configuration value read at startup. | Optional |
| VAMOOSE_TENANT | Configuration value read at startup. | Optional |
| VAMOOSE_TIMEZONE | Configuration value read at startup. | Optional |
| VAMOOSE_PROVIDER | Configuration value read at startup. | Optional |
| VAMOOSE_ICLOUD_USERNAME | Configuration value read at startup. | Optional |
| VAMOOSE_ICLOUD_APP_PASSWORD | Configuration value read at startup. | Optional |
| VAMOOSE_CALDAV_URL | Endpoint or connection string the server talks to. | Yes |
| VAMOOSE_CALDAV_USERNAME | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.