Clockify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOCKIFY_API_KEY | Yes | Your Clockify API key, which can be obtained from the Clockify User Settings under the 'API' section. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_user_time_entriesA | Find all time entries for a specific user by their name. Searches across a date range (defaults to last 30 days) and returns all time entries with descriptions, projects, and durations. |
| find_project_time_entriesA | Find all time entries for a specific project. Returns time entries from all users who have logged time to the project. |
| search_time_entriesA | Search time entries by description phrase. Searches across all users and returns entries containing the search phrase. |
| add_time_entryC | Add a time entry for a specific user. Creates a completed time entry with start and end times. |
| start_timerC | Start a timer for the current user. Creates a running time entry without an end time. |
| stop_timerB | Stop the currently running timer for the current user. |
| find_overtime_usersB | Find users who have logged more than a specified number of hours per week in the past month. Useful for identifying overworked team members. |
| find_undertime_usersB | Find users who have not logged at least a specified number of hours per week. Useful for identifying team members who may need support. |
| get_user_weekly_summaryC | Get a summary of hours logged by a user for each week in the past month. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no overlap: adding entries, starting/stopping timers, finding entries by project/user/search, identifying overtime/undertime users, and getting weekly summaries. The descriptions make it easy to differentiate between similar-sounding tools like find_user_time_entries and get_user_weekly_summary.
All tools follow a consistent snake_case pattern with clear verb_noun combinations (e.g., add_time_entry, find_project_time_entries, start_timer). The naming is predictable and readable throughout, with no deviations in style or convention.
With 9 tools, this server is well-scoped for time tracking and management. Each tool serves a specific, necessary function in the domain, from core operations like adding entries and managing timers to analytics features like finding overtime users and weekly summaries, without being overly sparse or bloated.
The tool set provides complete coverage for time tracking workflows: creating entries (add_time_entry, start_timer, stop_timer), retrieving entries by various criteria (find_project_time_entries, find_user_time_entries, search_time_entries), and analytics (find_overtime_users, find_undertime_users, get_user_weekly_summary). There are no obvious gaps, enabling agents to handle full CRUD-like operations and reporting.