MCP.so
ログイン

Tempo MCP Server

@ivelin-web

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

ivelin-web

Tempo MCP Server について

MCP server for managing Tempo worklogs in Jira

Tempo MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "tempo-mcp-server": {
      "command": "npx",
      "args": [
        "wrangler",
        "login"
      ]
    }
  }
}

Tempo MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Tempo MCP Server?

An MCP server for managing Tempo worklogs in Jira. It provides tools to track time and manage worklogs through Tempo’s API, accessible via Claude, Cursor, and other MCP-compatible clients.

How to use Tempo MCP Server?

Use one of three modes: deploy remotely on Cloudflare Workers (no install, each user gets a personal URL), run directly with npx, or clone the repository locally. Configure environment variables TEMPO_API_TOKEN, JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_BASE_URL.

Key features of Tempo MCP Server

  • Retrieve worklogs for a date range
  • Create, edit, and delete worklogs
  • Bulk create multiple worklogs in one operation
  • Missing days report (respects holidays via Tempo user-schedule)
  • Worklog analytics aggregated by issue, account, day, week, or month

Use cases of Tempo MCP Server

  • Log time against Jira issues directly from Claude conversations
  • Generate missing worklog reports to find under-logged working days
  • Analyze time distribution across projects and accounts
  • Automate bulk worklog creation for repeated time entries

よくある質問

1

What authentication methods does Tempo MCP Server support?

Basic auth (classic API token + email) is used for remote/Cloudflare deployment; OAuth 2.0 PKCE is supported only in stdio (local) modes.

2

What are the runtime requirements?

Node.js 18+ (LTS recommended) for local stdio modes. Remote mode runs on Cloudflare Workers with no Node dependency at runtime.

3

Where are user credentials stored in remote mode?

Credentials are AES-GCM encrypted with an `ENCRYPTION_KEY` and stored in Cloudflare KV under per-user keys. The personal MCP URL carries the credential — treat it like a password.

4

Can I host this server myself?

Yes. Fork the repository and deploy to Cloudflare Workers. Free-tier Workers (100k requests/day) and KV (100k reads/day) are sufficient.

5

Are there known transport or rate limits?

Remote mode uses Cloudflare’s native Rate Limiting binding (5 POST/min on `/setup`). Per-IP rate limits apply. The free Workers plan has a 50ms CPU limit per request but is I/O‑bound, so it works comfortably.

コメント

「その他」の他のコンテンツ