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

mcp-tempo-jira

v1.0.0

Published

MCP server for Tempo time tracking plugin and Jira

Readme

mcp-tempo-jira

MCP server for Tempo, the Jira time tracking plugin. Lets you manage worklogs directly from any MCP-compatible agent (Claude Desktop, Claude Code, Cursor, etc.).

Tools

Worklogs

| Tool | Description | | ---------------------- | ---------------------------------------------------------------------- | | get_user_worklogs | Get worklogs for the authenticated user | | list_worklogs | List worklogs with simple filters (date range, issue IDs, project IDs) | | search_worklogs | Search worklogs with advanced filters including multiple authors | | get_worklog | Get a single worklog by ID | | create_worklog | Create a new worklog for the authenticated user | | bulk_create_worklogs | Create multiple worklogs for the same issue at once (max 50) | | update_worklog | Update an existing worklog by ID | | delete_worklog | Delete an existing worklog by ID |

See docs/worklogs.md for detailed parameter reference.

Work Attributes

| Tool | Description | | ---------------------- | ------------------------------------------------------- | | list_work_attributes | List all work attributes defined in the Tempo workspace |

See docs/work-attributes.md for detailed parameter reference.

Configuration

Environment variables

| Variable | Required | Description | How to obtain | | ----------------- | -------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | TEMPO_API_TOKEN | Yes | Tempo API integration token | Go to Tempo → Settings → API Integration and generate a new token. The token requires read and write permissions for the Worklogs scope | | ACCOUNT_JIRA_ID | Yes | Your Jira account ID | Go to https://home.atlassian.com, open your profile — the URL will look like https://home.atlassian.com/o/<orgId>/people/<accountId>. Copy the last path segment as your account ID |

Claude Desktop

Add the following to your claude_desktop_config.json (usually at ~/Library/Application Support/Claude/claude_desktop_config.json):

{
	"mcpServers": {
		"mcp-tempo-jira": {
			"command": "npx",
			"args": ["-y", "mcp-tempo-jira"],
			"env": {
				"TEMPO_API_TOKEN": "your_tempo_token",
				"ACCOUNT_JIRA_ID": "your_jira_account_id"
			}
		}
	}
}

Claude Code

Both options save to ~/.claude.json and are available across all your projects.

Option 1 — Add the server and set environment variables manually:

claude mcp add --scope user mcp-tempo-jira -- npx -y mcp-tempo-jira

Then open ~/.claude.json and add the environment variables under the mcp-tempo-jira entry:

{
  "mcpServers": {
    "mcp-tempo-jira": {
      "command": "npx",
      "args": ["-y", "mcp-tempo-jira"],
      "env": {
        "TEMPO_API_TOKEN": "your_tempo_token",
        "ACCOUNT_JIRA_ID": "your_jira_account_id"
      }
    }
  }
}

Option 2 — Add the server with environment variables inline:

claude mcp add --scope user mcp-tempo-jira -e TEMPO_API_TOKEN=your_tempo_token -e ACCOUNT_JIRA_ID=your_jira_account_id -- npx -y mcp-tempo-jira

Development

See docs/development.md for setup, local testing with MCP Inspector, and how to test with Claude Code.

References