MCP Server
Connect Claude Desktop, Cursor, and other AI clients to Vacation Tracker over the Model Context Protocol.
Vacation Tracker runs an MCP (Model Context Protocol) server at https://mcp.vacationtracker.io. Any MCP client (Claude Desktop, Claude Code, Cursor, others) can ask it about your company's people, leaves, and public holidays straight from a chat. No browser tab, no manual export.
The server is read-only today. It will not create, update, or delete anything.
How it works
- Your AI client connects to
https://mcp.vacationtracker.io/mcp. - On first use, the client performs an OAuth2 authorization flow (RFC 8414 discovery, RFC 7591 Dynamic Client Registration, PKCE, authorization code) against
https://auth.vacationtracker.io. - You log in to Vacation Tracker and grant the requested scopes on the consent screen.
- The client exchanges the code for a Bearer token and calls MCP tools on your behalf.
- Each tool call is authorized against your Vacation Tracker role. Non-admin users only see the data they'd see in the web app.
It's the standard MCP OAuth handshake. No manual configuration, API keys, or shared secrets.
Available tools
The server ships four tools. See Tools for input/output schemas and LLM-facing descriptions.
| Tool | Scope | What it does |
|---|---|---|
get_workspace_info | mcp:workspace:read | List departments, locations, and leave types |
find_users | mcp:users:read | Look up people by name, email, department, or location |
get_leaves | mcp:leaves:read | Query leaves (approved, pending, or denied) in a date range |
get_holidays | mcp:workspace:read | Public holidays per location for a calendar year |
Tools accept names or IDs wherever a reference is expected, so "Engineering" works just as well as team-abc. If a name is ambiguous, the server returns a structured error with candidate matches and the LLM can retry with a specific one. Date shortcuts like today, this_week, next_month, and last_week resolve in the workspace's default-location timezone.
Prerequisites
- A Vacation Tracker account on the Core or Complete plan.
- An MCP-capable AI client. Claude Desktop is the reference client; Cursor supports MCP directly too. Any client that implements the MCP Streamable HTTP transport and OAuth2 PKCE with Dynamic Client Registration should work.
MCP is available to every Vacation Tracker account on a paid plan. There is no separate enablement step or feature flag.
Next steps
- Setup: connecting Claude Desktop and Cursor.
- Tools: full reference with input schemas and example outputs.
- Scopes: what each scope grants and how it maps to UI permissions.
- Troubleshooting: common errors and the
supportblock on error responses.