home / mcp / clockify master mcp server
Clockify Master MCP
Configuration
View docs{
"mcpServers": {
"hongkongkiwi-clockify-master-mcp": {
"command": "npx",
"args": [
"@hongkongkiwi/clockify-master-mcp"
],
"env": {
"MAX_TOOLS": "20",
"READ_ONLY": "false",
"ENABLED_TOOLS": "start_timer,stop_timer,get_today_entries",
"DISABLED_TOOLS": "bulk_edit_time_entries",
"CLOCKIFY_REGION": "global",
"ALLOWED_PROJECTS": "proj-123,proj-456",
"CLOCKIFY_API_KEY": "your_api_key_here",
"CLOCKIFY_API_URL": "https://api.clockify.me",
"ALLOWED_WORKSPACES": "ws-01,ws-02",
"DEFAULT_PROJECT_ID": "project-12345",
"DEFAULT_WORKSPACE_ID": "workspace-67890",
"ENABLED_TOOL_CATEGORIES": "user,workspace,timeEntry,project,report"
}
}
}
}Clockify Master MCP brings Clockifyβs time tracking, project management, and reporting capabilities directly into your Claude conversations. You can start timers, create projects, generate reports, and manage work without leaving your chat interface. This makes billing, planning, and daily workflows faster and more accurate by keeping everything in one place.
You will interact with Clockify Master MCP through Claude prompts. Start a timer, create projects, add clients, or generate reports by asking Claude to perform these actions. The MCP exposes a focused set of tools you can enable or restrict, so tailor the available actions to your needs. For example, start tracking time for a meeting, check todayβs entries, or export a project report as CSV. You can also manage workflows by tagging entries, assigning tasks, and reviewing team activity.
Prerequisites: you need Node.js installed on your machine, and you will run the MCP through a standard package manager. Ensure you have an API key ready if the MCP requires authentication.
{
"mcpServers": {
"clockify": {
"command": "npx",
"args": ["@hongkongkiwi/clockify-master-mcp"],
"env": {
"CLOCKIFY_API_KEY": "your_api_key_here"
}
}
}
}You can customize which features are exposed and how the MCP behaves within Claude. Use environment variables to enable or restrict tools, set default workspaces or projects, and control how many tools Claude can access at once.
# Example: restrict to a subset of projects and limit tools
{
"env": {
"CLOCKIFY_API_KEY": "your_api_key_here",
"DEFAULT_WORKSPACE_ID": "workspace-67890",
"ALLOWED_PROJECTS": "proj-123,proj-456",
"MAX_TOOLS": "20"
}
}If Claude cannot see Clockify tools, verify the configuration file location, restart Claude Desktop completely, check your API key, and ensure the MCP server name does not conflict with others.
If you encounter an invalid API key, generate a new key in Clockify, remove stray spaces, and confirm your account has the necessary permissions.
Starting your day you can say: Start tracking time for the morning standup meeting. Claude will begin the timer and attach it to the appropriate project.
Generating a weekly report: Ask for a weekly time report and export it as CSV. The MCP will compile hours by project and prepare the CSV for download.
Environment variables control access, scope, and behavior. Common variables include CLOCKIFY_API_KEY, ENABLED_TOOL_CATEGORIES, ALLOWED_PROJECTS, DEFAULT_WORKSPACE_ID, and READ_ONLY.
Start a new time entry with a description and optional project/workspace context
Stop the active time entry and save the entry details
Retrieve information about the current user
List time entries for today with optional filtering by project/workspace
Generate a summary report for a date range and export options
Create a new project within a workspace and assign a client
Modify project details while preserving essential associations with protection rules
Delete a project (subject to protection rules)
Archive an existing project to reduce clutter
List all projects in a workspace with filters
Add a new client and link to projects
Remove a client if not tied to protected projects
Create a time entry with a specific start time, duration, or end time
Edit existing time entries with safeguards to preserve project associations
Delete a time entry
Fetch details for a specific user
Switch the active workspace context for subsequent operations
Export a report in CSV format for sharing with stakeholders