Bring Scheduling Api
to Claude Desktop
Learn how to connect Timekit to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Timekit MCP Server?
Connect your Timekit account to any AI agent and simplify how you manage resource availability, booking workflows, and customer appointments through natural conversation.
What you can do
- Resource Management — List all resources (people, rooms, equipment) and create new profiles to manage scheduling capacity.
- Booking Lifecycle — Create new bookings, confirm tentative requests, or decline/cancel existing appointments via AI.
- Availability Checking — Programmatically find available time slots for one or more resources based on specific date ranges and durations.
- Rescheduling — Easily move existing bookings to new time slots without manual dashboard entry.
- Workflow Control — Manage complex booking 'graphs' (instant, confirm_decline) directly from your workspace.
- Account Visibility — Retrieve detailed metadata for specific bookings and resources to stay on top of your schedule.
How it works
1. Subscribe to this server
2. Enter your Timekit API Key (found in your developer settings)
3. Start managing your scheduling infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- Service Providers — quickly book client consultations and check availability via simple AI commands.
- Office Managers — manage room bookings and equipment scheduling across the organization directly from the workspace.
- Product Teams — automate the creation of resources and monitor booking flows via the AI assistant.
Built-in capabilities (11)
Cancel a confirmed booking
Check availability for resources
Confirm a pending booking
Create a new booking
Create a new resource
Decline a pending booking
Get details for a specific booking
Get details for a specific resource
List all bookings
List all resources (people, rooms, etc.)
Reschedule an existing booking
Why Claude Desktop?
Claude Desktop is the definitive way to connect Timekit to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Timekit in Claude Desktop
Timekit and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Timekit to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Timekit in Claude Desktop
The Timekit MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Timekit for Claude Desktop
Every tool call from Claude Desktop to the Timekit MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check availability for multiple resources at once?
Yes! Use the check_availability tool and provide a JSON array of Resource IDs. The agent will return time slots where all specified resources are available.
How do I confirm a tentative booking request?
Use the confirm_booking action and provide the unique Booking ID. This will transition the request from 'tentative' to 'confirmed' in your Timekit account.
Is it possible to reschedule an existing appointment via AI?
Absolutely. Use the reschedule_booking tool. Provide the Booking ID and the new start and end times to update the appointment instantly.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.