npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@d4works/mcp-clockify

v0.3.1

Published

MCP server for Clockify time tracking

Downloads

50

Readme

MCP Clockify Server

MCP server for Clockify time tracking integration with Claude.

Features

  • Start/Stop Timer - Track time on tasks identified by prefix (e.g., ABC-123)
  • Auto-create Tasks - Create new tasks when they don't exist
  • Time Multiplication - Duplicate time entries for billing adjustments
  • Self-configuration - Guided setup wizard for workspace and project selection

Installation

1. Get your Clockify API key

Get your API key here

2. Create or update .env file in your project

CLOCKIFY_API_KEY=your_api_key_here

3. Add to your project .mcp.json

{
  "mcpServers": {
    "clockify": {
      "command": "bash",
      "args": [
        "-c",
        "export $(cat .claude/.env.local | xargs) && npx -y @d4works/mcp-clockify@latest"
      ]
    }
  }
}

The source .env command loads your CLOCKIFY_API_KEY from the .env file before starting the server.

4. Restart Claude Code and configure

After restart, tell Claude to configure CLockify

The configuration wizard will guide you through selecting your workspace, project, task prefix, and language.

Available Tools

| Tool | Description | | ------------------------ | -------------------------------------------- | | test-connection | Test Clockify API connection | | get-running-timer | Check if a timer is running | | start-timer | Start timer for a task | | stop-timer | Stop running timer | | multiply-time | Duplicate last time entry | | create-task | Create new task in Clockify | | assign-task-to-running | Assign or change task on a running timer | | reconfigure | Change workspace/project settings |

Smart Timer Handling

When you try to start a timer while another is already running, the server will prompt you with options:

If the running timer has a task:

  • Stop running timer and start new one
  • Keep running timer

If the running timer has no task assigned:

  • Assign task to running timer (keeps the current time)
  • Stop running timer and start new one
  • Keep running timer

No changes are made without your explicit confirmation.

Usage Examples

Start tracking:

Start timer for task 123 with description "Implementing login form"

Stop timer:

Stop the timer

Check status:

What timer is currently running?

Development

Publishing a new release

# Login to npm (if not already logged in)
npm login

# Push changes and tag
git push && git push --tags

# Verify package contents
npm publish --dry-run

# Publish to npm
npm publish --access public

License

MIT