Clockify by Eduardo MCP Server

Manage Clockify time entries with Eduardo’s community MCP server. Follow its local TypeScript launch and Clockify API-token configuration.

Local serverstdio

What is the Clockify by Eduardo MCP Server?

Eduardo’s Clockify MCP server connects an assistant to Clockify time-entry workflows. It is a community source project, so its installation should follow that repository rather than assumptions about an official Clockify package. The README supplies a manual TypeScript launch and API configuration.

Keep time entries tied to the intended work

Specify the workspace, project, date and duration before recording time. Review existing entries for the same period to avoid overlapping hours. When preparing a timesheet, keep the original entry references and project names with the totals so a reviewer can trace the reported work.

Use the source-based configuration

The manual setup runs the checkout’s src/index.ts with tsx and the --local argument. Configure CLOCKIFY_API_URL and CLOCKIFY_API_TOKEN as shown by the maintainer. Replace the source path with the real checkout location. The README does not establish that a generic npm package with a similar name runs this project.

Maintainer’s setup and tool reference. Browse time tracking MCP servers for related workflows.

Configuration

The source checkout, tsx and a Clockify API token for the intended account.

VariableDescriptionRequired
CLOCKIFY_API_URLClockify API base URL used in the documented configuration.Check documentation
CLOCKIFY_API_TOKENClockify API token for the connected account.Yes

Example prompts to try

  • “Review the recorded time for this project and date before preparing a new time entry.”

Frequently asked questions

No. This is the community implementation in https-eduardo/clockify-mcp-server.