Skip to main content
Glama

tempo-mcp

Claude가 Jira 이슈에 대해 Tempo 작업 기록을 기록, 조회, 삭제할 수 있게 해주는 MCP 서버입니다.

설정

  1. npm install && npm run build

  2. .env.example을 .env로 복사하고 다음 항목을 입력하세요:

    • TEMPO_API_TOKEN — Jira의 Tempo → Settings → API Integration에서 생성하며, Manage Worklogs 권한으로 범위가 지정됩니다.

    • JIRA_BASE_URL — 예: https://your-domain.atlassian.net

    • JIRA_EMAIL / JIRA_API_TOKEN — 이슈 키(예: PROJ-1234)를 Tempo에서 요구하는 숫자 이슈 ID로 변환하는 데 사용됩니다. 토큰은 https://id.atlassian.com/manage-profile/security/api-tokens에서 생성하세요.

Related MCP server: jira-mcp-server

Claude Code에 등록

claude mcp add tempo-mcp -- node /path/to/tempo-mcp/dist/index.js

또는 위 환경 변수를 항목의 env 블록에 설정한 .mcp.json을 통해 등록할 수 있습니다.

도구

  • get_worklogs — 작업 기록을 조회하며, 선택적으로 issueKey, authorAccountId, 날짜 범위(from/to)로 필터링할 수 있습니다.

  • post_worklog — 이슈에 시간을 기록합니다 (issueKey, timeSpentSeconds, startDate, authorAccountId, 선택적으로 startTime/description).

  • delete_worklog — tempoWorklogId로 작업 기록을 삭제합니다.

이슈 키는 Jira REST API를 통해 Tempo에서 요구하는 숫자 이슈 ID로 자동 변환되며(프로세스 내에서 캐시됩니다).

Available Tools

3 tools
delete_worklogA

Delete a Tempo worklog by its Tempo worklog ID.

Inputs: tempoWorklogId (required).

get_worklogsA

Fetch Tempo worklogs, optionally filtered by Jira issue key, author account ID, and/or date range.

Inputs: to, from, limit, issueKey, +1 more.

post_worklogB

Log time in Tempo against a Jira issue on behalf of a given Jira account.

Inputs: issueKey (required), startDate (required), authorAccountId (required), timeSpentSeconds (required), +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation on worklogs: create (post), read (get), and delete. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern with clear verbs (post, get, delete) and the same noun base (worklog(s)). The plural in get_worklogs is semantically appropriate for fetching multiple records.

    Tool Count5/5

    Three tools is a well-scoped set for a focused worklog integration. Each tool covers an essential action without unnecessary bloat.

    Completeness3/5

    The set covers create, read, and delete but lacks an update operation, which is a notable gap for worklog management. Agents must work around this by deleting and recreating worklogs, which is not always desirable.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with Jira for project management tasks, including issue creation, updates, workflow transitions, and bulk operations.
      4
      MIT