Clockify

Provides MCP endpoints to interact with Clockify: fetch user info, list workspace projects, and log time entries.

javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "yravinderkumar33-clockify-mcp-server": {
      "command": "clockify-mcp-server",
      "args": [],
      "env": {
        "CLOCKIFY_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

You run a modular MCP server that connects to the Clockify time tracking API, exposing focused tools to fetch user info, list projects, and log time entries. This server lets MCP clients interact with Clockify in a structured, validated way, enabling automation and composable workflows without writing custom API calls.

How to use

You configure your MCP client to connect to the Clockify MCP Server. Use the provided tool names to perform common actions: retrieve your current Clockify user information, fetch all projects within a workspace, and log time entries with dates, descriptions, and project/workspace associations. Each tool validates its inputs and returns structured results to help you build reliable automation.

How to install

Prerequisites: Node.js 18.0.0 or higher and a Clockify API key.

Install the MCP server globally from npm

npm install -g clockify-mcp-server

Run from source

If you prefer to run from source, clone the project, install dependencies, and start the server.

git clone https://github.com/yravinderkumar33/clockify-mcp-server.git
cd clockify-mcp-server
npm install
npm start

Configure environment and run locally

Set your Clockify API key in the environment so the server can authenticate with Clockify.

export CLOCKIFY_API_KEY=your_api_key_here

Start using with an MCP client

After starting the server, configure your MCP client to connect using the embedded configuration example. The server runs locally and is intended to be used by clients as an MCP endpoint.

Additional configuration notes

The server exposes a minimal runtime surface and relies on explicit environment configuration for the Clockify API key. If you run into issues, ensure the API key is valid and that the server process has access to it in its environment.

Tools and usage overview

The MCP server provides three tools for Clockify integration: iam to fetch the current user information, getAllProjects to list all projects in a workspace, and logTimeEntry to create time entries with defined date, time window, project, and workspace.

Security and best practices

Protect your API key as you would any secret. Do not commit it to source control and restrict server access to trusted clients. Rotate the API key if you suspect it may be compromised.

Troubleshooting

If you encounter authentication errors, verify CLOCKIFY_API_KEY is set correctly in the environment where the MCP server runs. Check that the key has the appropriate permissions in Clockify and that the server process can access the environment variable.

Notes

This server is designed to be used with MCP clients that support the standard MCP configuration object. The clockify-mcp-server executable serves as the runtime for the client-side integration.

Available tools

iam

Fetch current user information from Clockify API to identify the authorized user and usable workspaces.

getAllProjects

Retrieve all projects for a specified Clockify workspace by providing the workspaceId.

logTimeEntry

Create a Clockify time entry with date, description, projectId, workspaceId, and optional startTime/endTime.