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 from your Clockify profile settings |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userB | Get information about the current user |
| get_workspacesB | Get all workspaces for the current user |
| get_workspace_usersC | Get all users in a workspace |
| create_time_entryC | Create a new time entry |
| get_time_entriesC | Get time entries for a user |
| update_time_entryC | Update an existing time entry |
| delete_time_entryC | Delete a time entry |
| stop_time_entryC | Stop a running time entry |
| duplicate_time_entryC | Duplicate a time entry |
| create_projectC | Create a new project |
| get_projectsC | Get all projects in a workspace |
| get_projectC | Get a specific project by ID |
| update_projectC | Update an existing project |
| delete_projectC | Delete a project |
| create_taskC | Create a new task in a project |
| get_tasksC | Get all tasks in a project |
| get_taskB | Get a specific task by ID |
| update_taskC | Update an existing task |
| delete_taskC | Delete a task |
| create_clientC | Create a new client |
| get_clientsC | Get all clients in a workspace |
| update_clientC | Update an existing client |
| delete_clientC | Delete a client |
| create_tagC | Create a new tag |
| get_tagsC | Get all tags in a workspace |
| update_tagC | Update an existing tag |
| delete_tagC | Delete a tag |
| get_detailed_reportC | Generate a detailed time tracking report |
| get_summary_reportC | Generate a summary time tracking report |
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 29 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific resource (client, project, tag, task, time_entry, report, user, workspace) and action (create, get, update, delete, duplicate, stop), making it easy for an agent to select the correct tool without confusion.
Tool names follow a perfectly consistent verb_noun pattern throughout, such as create_client, get_clients, update_project, and delete_time_entry. This predictability enhances readability and usability for agents, with no deviations or mixed conventions.
With 29 tools, the count is borderline high for a time tracking server, feeling somewhat heavy. While it covers many operations, it might be overwhelming for agents, though it's not extreme like 50+ tools.
The tool set provides complete CRUD/lifecycle coverage for the Clockify domain, including clients, projects, tags, tasks, time entries, reports, users, and workspaces. There are no obvious gaps, and agents can handle all core workflows without dead ends.