# Claude MCP connector

> Connect Claude to Vaia with a personal API key: setup, available tools for time tracking and leave, and security basics.

Public docs

Curated public guide — not the full private API documentation.

Vaia exposes a remote Model Context Protocol (MCP) endpoint so members can connect Claude (Desktop or claude.ai custom connector) with a personal API key and act through the same time-tracking and leave capabilities as the in-app assistant, under their live role permissions.

## Setup

1. In Vaia, open [Claude MCP](https://app.vaia.space/claude-mcp) and create an API key for the organization you want Claude to use. Copy the vaia\_mcp\_… secret when it is shown — it is displayed only once.
2. In Claude, add a custom connector (remote MCP / web).
3. Enter the connection details below. Choose no sign-in and set the request header.

- **Connector URL:**`https://api.vaia.space/mcp`
- **Request header name:**`X-API-KEY`
- **Request header value:** the raw vaia\_mcp\_… secret (no Bearer prefix).

Organization context is baked into the key. Create a separate key per organization if you belong to more than one.

## What you can do

Claude discovers tools after connecting. Availability depends on which modules your organization has enabled and which permissions your role holds. Actions are always for you — never on behalf of another member.

### Time tracking

Start and stop timers, check status, resume from today’s last log, summarize your time, create completed logs, and submit timesheets when a project requires them.

- `timer_start`
- `timer_stop`
- `timer_status`
- `timer_resume`
- `timelog_summary`
- `timelog_create`
- `timesheet_weeks_status`
- `timesheet_submit`

### Leave

Check balances, list and request leave, see upcoming approved leave, cancel pending requests, and shorten approved leave when returning early.

- `leave_balance`
- `leave_request`
- `leave_requests_list`
- `leave_upcoming`
- `leave_request_cancel`
- `leave_request_shorten`

Not included in this connector: accounting, invoices, HR, inventory, documents, workflows, org admin, and other modules beyond time tracking and leave.

## Security

- Treat the API key like a password. It is shown once at creation; regenerate (create a new key and revoke the old one) if you lose it.
- Keys work only on the MCP endpoint (/mcp), not on ordinary Vaia REST API routes.
- Revoke keys you no longer use, or if a device is lost or a secret may have leaked. At most five active keys per membership.
- Review Claude’s tool-approval prompts before allowing writes (timers, leave requests, timesheet submit).
- The MCP endpoint is rate-limited (60 requests per minute).

## Example prompts

- Start my timer on Project X.
- How much leave do I have left this year?
- Request vacation next Monday through Wednesday.
- Is my timer running?

Make your next move

## Good things start together.

Be among the first to bring your team into Vaia.

---

Canonical: https://vaia.space/public/claude-mcp
Index: https://vaia.space/llms.txt