Bring Time Tracking
to Claude Desktop
Learn how to connect TrackingTime to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the TrackingTime MCP Server?
Connect your TrackingTime account to any AI agent and simplify how you manage your productivity, project tasks, and billable hours through natural conversation.
What you can do
- Live Tracking — Start and stop timers for specific tasks instantly via AI commands to track your real-time activity.
- Task Management — Create, list, and update tasks, and organize them into specific projects for better workflow.
- Time Logging — Retrieve detailed logs of your time entries for any date range and manually add missing blocks of time.
- Project & Client Oversight — List all projects and customers to manage your business directory and assignments.
- Team Coordination — Query workspace users to understand team structure and member availability.
- Account Visibility — Fetch your user profile and verify account configurations directly from the agent.
How it works
1. Subscribe to this server
2. Enter your TrackingTime Email and Password
3. Start managing your time and productivity from Claude, Cursor, or any MCP client
Who is this for?
- Freelancers & Consultants — quickly start timers and log billable hours via simple AI commands.
- Project Managers — monitor task progress and project logs across the team directly from the workspace.
- Productivity Junkies — keep an organized record of daily activities and time spent on specific projects via the AI assistant.
Built-in capabilities (12)
Manual time entry
Add new project
Add new task
Get current user
List project clients
List your projects
List your tasks
Get time logs
List team members
Start tracking time
Stop tracking time
Modify task
Why Claude Desktop?
Claude Desktop is the definitive way to connect TrackingTime to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 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
TrackingTime in Claude Desktop
TrackingTime and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TrackingTime 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 TrackingTime in Claude Desktop
The TrackingTime 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 12 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
TrackingTime for Claude Desktop
Every tool call from Claude Desktop to the TrackingTime MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I start a timer for a specific task using the AI?
Yes! Use the start_timer tool and provide the Task ID. Your agent will instantly begin tracking time for that specific activity in your workspace.
How do I see my time logs for the last 7 days?
Run the list_time_entries query. Provide the fromDate and toDate in YYYY-MM-DD format to retrieve the full history of tracked blocks for that period.
Is it possible to add a time entry manually via AI?
Absolutely. Use the add_time_entry action. Provide the start time, end time, and the associated Task ID to register a completed block of time.
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.