MCP.so
ログイン

Jira Weekly Reporter MCP Server

@Jongryong

基本情報

カテゴリ

バージョン管理

トランスポート

stdio

作者

Jongryong

Jira Weekly Reporter MCP Server について

Jira Weekly Reporter MCP Server

Jira Weekly Reporter MCP Server の設定

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

{
  "mcpServers": {
    "jira_reporter": {
      "command": "uv",
      "args": [
        "pip",
        "install",
        "fastmcp",
        "jira[cli]",
        "python-dotenv",
        "httpx",
        "anyio"
      ]
    }
  }
}

Jira Weekly Reporter MCP Server のツール

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

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

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Jira Weekly Reporter MCP Server?

A FastMCP server that connects to Jira (Cloud or Server/Data Center) to generate weekly reports based on issue activity. It uses the pycontribs-jira library and can optionally leverage the connected client's LLM for summarizing the report. Designed for developers and project managers who need automated Jira reporting via MCP‑compatible clients like Claude Desktop.

How to use Jira Weekly Reporter MCP Server?

Install Python 3.10+, fastmcp, and the listed dependencies. Create a .env file with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN. Run the server with python jira_reporter_server.py or fastmcp run jira_reporter_server.py. In an MCP client (e.g., Claude Desktop), invoke the generate_jira_report tool by name, optionally passing jql_query, project_key, max_results, or summarize parameters.

Key features of Jira Weekly Reporter MCP Server?

  • Connects securely via API tokens stored in a .env file.
  • Exposes a generate_jira_report tool accessible over MCP.
  • Defaults to issues updated in the last 7 days.
  • Supports custom JQL queries and project‑specific filtering.
  • Limits result count (configurable, default 50).
  • Optionally requests a summary from the client’s LLM.

Use cases of Jira Weekly Reporter MCP Server?

  • Generate weekly status reports for a project without manual JQL construction.
  • Quickly retrieve recently updated issues and ask an LLM for a plain‑language summary.
  • Integrate Jira reporting into AI‑powered chat assistants (e.g., Claude Desktop) for on‑demand updates.
  • Automate recurring report generation by calling the tool from an MCP script or workflow.

よくある質問

1

What Jira versions are supported?

The server supports Jira Cloud, Jira Server, and Jira Data Center. Authentication requires an API token (Cloud) or Personal Access Token (Server/DC).

2

How do I authenticate to Jira?

Place your Jira URL, username (email for Cloud), and an API token or PAT in a `.env` file in the same directory as the server script. The server reads these credentials on startup.

3

Can I customize the report query?

Yes. The `jql_query` parameter lets you supply any valid JQL. A `project_key` parameter can further limit results to a specific project. The default query covers issues updated in the last 7 days.

4

Does the server require an LLM to work?

No. The optional `summarize` parameter, if set to `true`, asks the client’s LLM (via `ctx.sample()`) for a summary. Without it, the tool returns raw issue data.

5

What is the maximum number of issues returned?

The `max_results` parameter controls this; the default is 50. You can increase or decrease it as needed.

コメント

「バージョン管理」の他のコンテンツ