Clockify MCP Server

Get project Clockify config

clockify_get_config

Retrieve effective .clockify/config.yml standards from a repository to see per-method descriptions, task, rounding, overlap, and automation. Set config_root to the repo's git toplevel.

Instructions

Returns the effective .clockify/config.yml standards (per-method description, task, rounding, overlap, automation). Pass config_root as that repo's git toplevel when this MCP is user-scoped.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clockify_get_config"
  }
}

Input Schema

Name	Required	Description	Default
`config_root`	No	Absolute git toplevel of the repo that contains .clockify/config.yml. Resolve once per session with `git rev-parse --show-toplevel` from the working directory (open tabs are not required); reuse that string on later calls unless the repo or focused root changed. Do not pass a multi-root .code-workspace folder.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Aug 21, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / config_root

Added value: +{
+  "description": "Absolute git toplevel of the repo that contains .clockify/config.yml. Resolve once per session with `git rev-parse --show-toplevel` from the working directory (open tabs are not required); reuse that string on later calls unless the repo or focused root changed. Do not pass a multi-root .code-workspace folder.",
+  "type": "string"
+}

First observedv0.1.0Aug 10, 2026

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly indicates this is a read operation returning an 'effective' configuration, which implies merged/default behavior rather than raw file contents. However, it doesn't disclose what happens if the config file is missing, whether any parsing or fallback occurs, or whether there are any side effects; for a read-only getter, the main gaps are inconsequential but still unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, concise and information-dense. The first sentence states what is returned and the second adds the exact config_root usage condition. No filler or repeated schema content from the description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is a simple one-parameter getter with no output schema and no annotations, the description covers the core domain (what config it returns, where it comes from, how to point at it). It is slightly light on defining how the configuration is represented when 'effective' merges sources, but for this complexity, the description is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema's description of `config_root` is already comprehensive—it defines the type, absolute git toplevel semantics, how to resolve it, reuse over calls, and what to avoid. The tool description adds the user-scoped tip but otherwise does not materially expand beyond the schema. With 100% schema coverage, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Returns' is specific and the description names the exact resource: the effective `.clockify/config.yml` standards, including the four areas covered (per-method description, task, rounding, overlap, automation). This distinguishes the tool from all sibling Clockify tools, none of which read configuration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly explains when to pass `config_root` and how to determine it, including the required git toplevel semantics and the user-scoped caveat. There is no competing config tool among the siblings, so explicit 'use instead of' guidance is not necessary. However, it doesn't state scenarios where calling the tool might be unnecessary or where the config might be absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server