generate_jira_reportLABSCO SUMMARY
The summary is written by your model, not by a service.
Asking the connected client to do the summarisation means the report never leaves your model's context for a third-party API, and there is no second key to manage or bill. The default JQL is a sensible weekly window, but the parameter is there — pointing it at a sprint, a component or a person is the same call with a different query.
What it is
A small server built on FastMCP that connects to a Jira instance, Cloud or Server/Data Center, and turns issue activity into a report. Its one distinguishing move is summarisation: rather than calling a model of its own, it asks the connected client's model to summarise the report it just produced.
What you get
- A report of Jira issues, defaulting to
updated >= -7d ORDER BY updated DESCwhen you supply nothing —generate_jira_report - A custom JQL query when you want a different window or filter, passed as
jql_query - The search scoped to one project by key, passed as
project_key - A cap on how many issues go into the raw report, via
max_results, defaulting to 50 - An optional summary produced by your own client's model when
summarizeis true, so no second API key is involved
Requirements
Access to a Jira instance and an API token — an Atlassian API token for Cloud, or a Personal Access Token for Server and Data Center. Put JIRA_URL, JIRA_USERNAME and JIRA_API_TOKEN in a .env file beside the server script, and keep that file out of version control. Python 3.10 or later, with dependencies installed via uv pip install fastmcp "jira[cli]" python-dotenv httpx anyio, and the FastMCP CLI on your PATH since the documented client config launches fastmcp run against the script's absolute path. An SSE transport option is available for remote use.
Setup effort
Build from source — git clone https://github.com/Jongryong/jira_reporter.git
USE CASES
01
Writing the weekly status update
Take everything updated in the last seven days and have it summarised in the same conversation you will paste the update into.
02
Reporting on one project rather than the whole instance
Scope by project key so a report covers a single team without hand-writing the JQL clause.
03
Answering a specific question about issue activity
Pass your own JQL — a label, an assignee, a fix version — and read the matching issues back.
04
Keeping a large report readable
Lower the result cap so the raw report stays inside a comfortable context size before it is summarised.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
Python 3.10
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/Jongryong/jira_reporter.git
cd jira_reporter
pip install fastmcp "jira[cli]" python-dotenv httpx anyioCreate a .env file next to jira_reporter_server.py with JIRA_URL, JIRA_USERNAME and JIRA_API_TOKEN
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"jira_report": {
"command": "fastmcp",
"args": [
"run",
"<YOUR_PATH_TO_JIRA_REPORTER_SERVER>"
]
}
}
}
