Tiny fun thing for today’s Google I/O keynote.
It counts how many times “AI” / “A.I.” / “artificial intelligence” gets said, highlights transcript lines, has a prediction pool, chat, and buzzword bingo.
Join before the keynote and lock your prediction:
I’m guessing 666.
I built a small open-source MCP server for Jira Tempo.
The reason was pretty simple: I didn't want to manually log time every day anymore.
It's not difficult, but it is repetitive. Open Jira, find the issue, open Tempo, create the worklog, write the description, repeat the same thing tomorrow.
Since I already use Claude and agents for parts of my workflow, I wanted to move this into the same flow. Now after finishing a work session, I can ask the agent to log the time instead of doing it manually.
Current tools:
- create worklog
- bulk create worklogs
- retrieve worklogs
- edit/delete worklogs
- find missing worklog days
- get basic worklog analytics
It supports Claude, Codex, Cursor and any other MCP-compatible clients.
I’m sharing it mostly to get feedback from people building or using MCP workflows. Curious if others are automating similar small but annoying dev admin tasks.
Repo:
I built a small MCP server for Jira Tempo because I was tired of manually logging my time every day.
Not a huge problem, just one of those small repetitive tasks that slowly becomes annoying:
open Jira -> find the issue -> open Tempo -> add the worklog -> write the description -> repeat tomorrow.
I use agents a lot in my workflow, so I wanted to make this part more natural. Instead of logging time manually, I can now finish my work session and ask the agent to log the time for me.
The server currently supports:
- retrieving worklogs
- creating worklogs
- bulk creating worklogs
- editing/deleting worklogs
- finding missing worklog days
- basic worklog analytics
It works with Claude, Codex, Cursor and any other MCP-compatible clients.
I made it open-source because I figured other people using Jira + Tempo might have the same annoying workflow. I'm also curious what features would make this more useful for real teams.
Repo:
https://github.com/ivelin-web/tempo-mcp-server
Would appreciate feedback, ideas, or contributions.