backlog-mcp 1.0.1__tar.gz → 1.0.3__tar.gz

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/.env.example

@@ -1,4 +1,3 @@
 # Backlog API Settings
 BACKLOG_API_KEY=your_backlog_api_key_here
 BACKLOG_DOMAIN=your-space.backlog.com
-USER_ID=your_user_id

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlog-mcp
-Version: 1.0.1
+Version: 1.0.3
 Summary: A Model Context Protocol (MCP) server for Backlog project management integration
 Author-email: BaoNguyen <baonguyen@teqnological.asia>
 Requires-Python: <3.14,>=3.13
@@ -55,22 +55,9 @@ Get detailed information about a Backlog issue by its issue key.
 
 ### `get_user_issue_list`
 
-Retrieve a filtered list of issues based on project, assignees, milestones, and other criteria.
+Retrieve a list of issues assigned to the current user.
 
-**Parameters:**
-- `project_ids` (List[int], optional): List of project IDs.
-- `assignee_ids` (List[int], optional): List of assignee IDs (defaults to current user).
-- `status_ids` (List[int], optional): List of status IDs (defaults to non-closed).
-- `milestone_ids` (List[int], optional): List of milestone IDs.
-- `parent_issue_ids` (List[int], optional): List of parent issue IDs.
-- `created_since` (str, optional): Created since (YYYY-MM-DD).
-- `created_until` (str, optional): Created until (YYYY-MM-DD).
-- `updated_since` (str, optional): Updated since (YYYY-MM-DD).
-- `updated_until` (str, optional): Updated until (YYYY-MM-DD).
-- `start_date_since` (str, optional): Start Date since (YYYY-MM-DD).
-- `start_date_until` (str, optional): Start Date until (YYYY-MM-DD).
-- `due_date_since` (str, optional): Due Date since (YYYY-MM-DD).
-- `due_date_until` (str, optional): Due Date until (YYYY-MM-DD).
+This tool automatically determines the current user's ID and returns only issues assigned to that user. No parameters are required.
 
 ## Running the Server Locally
 
@@ -89,13 +76,11 @@ Create a `.env` file in the root directory and add the following environment var
 # Backlog API Settings
 BACKLOG_API_KEY=your_backlog_api_key_here
 BACKLOG_DOMAIN=your-space.backlog.com
-USER_ID=your_user_id
 ```
 
 > **Important:**
 > - Replace `your_backlog_api_key_here` with your actual Backlog API key
 > - Replace `your-space.backlog.com` with your actual Backlog domain
-> - Replace `your_user_id` with your actual Backlog user ID
 
 ### 3. Start the server
 

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/README.md

@@ -39,22 +39,9 @@ Get detailed information about a Backlog issue by its issue key.
 
 ### `get_user_issue_list`
 
-Retrieve a filtered list of issues based on project, assignees, milestones, and other criteria.
+Retrieve a list of issues assigned to the current user.
 
-**Parameters:**
-- `project_ids` (List[int], optional): List of project IDs.
-- `assignee_ids` (List[int], optional): List of assignee IDs (defaults to current user).
-- `status_ids` (List[int], optional): List of status IDs (defaults to non-closed).
-- `milestone_ids` (List[int], optional): List of milestone IDs.
-- `parent_issue_ids` (List[int], optional): List of parent issue IDs.
-- `created_since` (str, optional): Created since (YYYY-MM-DD).
-- `created_until` (str, optional): Created until (YYYY-MM-DD).
-- `updated_since` (str, optional): Updated since (YYYY-MM-DD).
-- `updated_until` (str, optional): Updated until (YYYY-MM-DD).
-- `start_date_since` (str, optional): Start Date since (YYYY-MM-DD).
-- `start_date_until` (str, optional): Start Date until (YYYY-MM-DD).
-- `due_date_since` (str, optional): Due Date since (YYYY-MM-DD).
-- `due_date_until` (str, optional): Due Date until (YYYY-MM-DD).
+This tool automatically determines the current user's ID and returns only issues assigned to that user. No parameters are required.
 
 ## Running the Server Locally
 
@@ -73,13 +60,11 @@ Create a `.env` file in the root directory and add the following environment var
 # Backlog API Settings
 BACKLOG_API_KEY=your_backlog_api_key_here
 BACKLOG_DOMAIN=your-space.backlog.com
-USER_ID=your_user_id
 ```
 
 > **Important:**
 > - Replace `your_backlog_api_key_here` with your actual Backlog API key
 > - Replace `your-space.backlog.com` with your actual Backlog domain
-> - Replace `your_user_id` with your actual Backlog user ID
 
 ### 3. Start the server
 

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/app/server_settings.py

@@ -13,7 +13,4 @@ class ServerSettings(BaseSettings):
     BACKLOG_API_KEY: str
     BACKLOG_DOMAIN: str  # e.g., "your-space.backlog.com"
 
-    # User Settings
-    USER_ID: int
-
 settings = ServerSettings()

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/app/tools/get_issue_details.py

@@ -4,7 +4,6 @@ from app.utils.ultils import get_issue_detail_handler
 
 async def get_issue_details(
     issue_key: str,
-    issue_title: str | None,
     timezone: str = "UTC"
 ):
     """
@@ -12,17 +11,11 @@ async def get_issue_details(
 
     Args:
         issue_key (str): The key of the Backlog issue to retrieve.
-        issue_title (str): The title of the Backlog issue, used for logging or reference purposes.
         timezone (str, optional): The timezone to format datetime fields. Defaults to "UTC".
     """
     try:
-        if not issue_key and not issue_title:
+        if not issue_key:
             raise ValueError("Please provide an issue key.")
-        elif issue_title and not issue_key:
-            raise ValueError(
-                "Cannot retrieve task information with only the issue title. "
-                "Please provide an issue key. Searching by title is not supported yet."
-            )
         ctx = create_backlog_context()
         result = await get_issue_detail_handler(
             backlog_domain=ctx.backlog_domain,

backlog_mcp-1.0.3/app/tools/get_user_issue_list.py

@@ -0,0 +1,28 @@
+from app.utils.di import create_backlog_context
+from app.utils.ultils import get_user_task, get_current_user
+
+
+async def get_user_issue_list():
+    """
+    Retrieves a list of issues assigned to the current user from Backlog.
+
+    This function automatically determines the current user's ID via API
+    and returns only issues assigned to that user.
+    """
+
+    try:
+        ctx = create_backlog_context()
+
+        # Fetch current user information
+        current_user = await get_current_user(ctx.backlog_domain, ctx.api_key)
+        current_user_id = current_user["id"]
+
+        # Get issues assigned to current user
+        issue_list = await get_user_task(
+            backlog_domain=ctx.backlog_domain,
+            api_key=ctx.api_key,
+            assignee_ids=[current_user_id]
+        )
+        return issue_list
+    except Exception as e:
+        raise e

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/app/utils/ultils.py

@@ -46,8 +46,9 @@ def time_in_range(time: str, start_range: str, end_range: str):
     return start_range_time <= time_to_be_compared <= end_range_time
 
 
-def process_issue_detail(issue_detail, timezone):
+def process_issue_detail(issue_detail, timezone, issue_key):
     processed_issue = {
+        "issue_key": issue_key,
         "summary": issue_detail["summary"],
         "description": issue_detail["description"]
     }
@@ -108,7 +109,7 @@ async def get_issue_detail_handler(
                 comments_in_time_range.append(comment)
 
             issue_detail.update({"comments": comments_in_time_range})
-            processed_detail = process_issue_detail(issue_detail, timezone)
+            processed_detail = process_issue_detail(issue_detail, timezone, issue_key)
             return processed_detail
 
         except Exception as e:
@@ -266,3 +267,27 @@ async def get_project_list(backlog_domain: str, api_key: str) -> list[int]:
             raise ValueError(f"Failed to get project list: {e}") from e
         except Exception as e:
             raise ValueError(f"Unexpected error while getting project list: {e}") from e
+
+
+async def get_current_user(backlog_domain: str, api_key: str) -> dict:
+    """Get current user information from Backlog API.
+
+    Returns:
+        dict: {"id": int, "name": str}
+    """
+    url = f"{backlog_domain}api/v2/users/myself"
+    params = {"apiKey": api_key}
+
+    async with httpx.AsyncClient() as client:
+        try:
+            response = await client.get(url, params=params, timeout=10.0)
+            response.raise_for_status()
+            data = response.json()
+            return {
+                "id": data["id"],
+                "name": data["name"]
+            }
+        except httpx.HTTPError as e:
+            raise ValueError(f"Failed to get current user: {e}") from e
+        except Exception as e:
+            raise ValueError(f"Unexpected error while getting current user: {e}") from e

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/docs/mcp-installer-template.md

@@ -5,8 +5,9 @@
 This template allows LLMs to generate interactive installation scripts **exclusively for PyPI-published MCP servers**. The template file is typically placed in the repository of a PyPI project.
 
 **Important**: 
-- This template is **PyPI-only**. It always uses the Standard Template Structure with `--index-url` and `--extra-index-url` arguments.
+- This template is **PyPI-only** for production packages on pypi.org
 - MCP configuration JSONs from Cline, GitHub Copilot, or Claude Code do NOT include an `env` field by default. The LLM must ask the user about environment variables and how to handle them.
+- **The MCP_NAME must match the PyPI package name exactly** for uvx to work correctly
 
 The generated script will:
 
@@ -75,7 +76,7 @@ The generated script will:
    - If **No**: Skip env var section entirely (script will have no env section)
 
 3. **Replace placeholders** in the template below with actual values based on user's answers:
-   - `{{MCP_NAME}}` - The MCP server name (e.g., "backlog-mcp")
+   - `{{MCP_NAME}}` - The MCP server name (e.g., "backlog-mcp") - **must match PyPI package name**
    - `{{MCP_DISPLAY_NAME}}` - Human-readable name (e.g., "Backlog MCP")
    - `{{COMMAND}}` - The command (usually "uvx")
    - `{{ARGS}}` - Array of command arguments
@@ -87,15 +88,15 @@ The generated script will:
    - `{{TIMEOUT_VALUE}}` - Timeout value if present
    - `{{HAS_TYPE}}` - "true" or "false" based on config
 
-3. **Generate the script** by replacing all placeholders with actual values
+4. **Generate the script** by replacing all placeholders with actual values
 
-4. **Save as** `install-{{MCP_NAME}}.sh` and make it executable
+5. **Save as** `install-{{MCP_NAME}}.sh` and make it executable
 
 ---
 
 ## Standard Template Structure
 
-**IMPORTANT**: This template is for PyPI-published MCP servers only. You **MUST** always use the following canonical args structure. This ensures consistent installation across all PyPI-published MCP servers.
+**IMPORTANT**: This template is for PyPI-published MCP servers only.
 
 ### Required Args Format
 
@@ -103,26 +104,24 @@ The `args` array **MUST** always follow this structure:
 
 ```json
 "args": [
-  "--from",
-  "{{PACKAGE_NAME}}@latest",
-  "--index-url",
-  "https://test.pypi.org/simple/",
-  "--extra-index-url",
-  "https://pypi.org/simple/",
-  "{{MCP_NAME}}"
+  "{{MCP_NAME}}@latest"
 ]
 ```
 
-**Placeholders:**
-- `{{PACKAGE_NAME}}`: The PyPI package name (e.g., `backlog-mcp`)
-- `{{MCP_NAME}}`: The MCP server identifier (usually same as package name, e.g., `backlog-mcp`)
+**Placeholder:**
+- `{{MCP_NAME}}`: The MCP server identifier (e.g., `backlog-mcp`)
+  - **Critical**: `{{MCP_NAME}}` **must match the PyPI package name exactly** for uvx to install correctly
 
 **Conversion to bash script format:**
 ```bash
-"--from" "{{PACKAGE_NAME}}@latest" "--index-url" "https://test.pypi.org/simple/" "--extra-index-url" "https://pypi.org/simple/" "{{MCP_NAME}}" "ENV_START"
+"{{MCP_NAME}}@latest" "ENV_START"
 ```
 
-**Note**: The `--index-url` and `--extra-index-url` arguments are **mandatory** and must always be included to ensure proper package resolution from both test.pypi.org and pypi.org.
+**Note**: Production mode is simple because the package name usually matches the MCP name, and pypi.org is the default package index. The `ENV_START` marker separates args from environment variables.
+
+**Examples:**
+- If PyPI package name is `backlog-mcp` → MCP_NAME must be `backlog-mcp`
+- If PyPI package name is `mcp-server-sqlite` → MCP_NAME must be `mcp-server-sqlite`
 
 ---
 
@@ -131,8 +130,9 @@ The `args` array **MUST** always follow this structure:
 **Important Notes:**
 1. Real MCP configurations from Cline/Copilot/Claude Code do NOT include an `env` field. The LLM must ask the user about environment variables separately.
 2. These examples show **reference configurations** that users might have. They are provided for reference only.
-3. **Always use the Standard Template Structure** (see above) regardless of what the user's config shows. The user's config may be outdated, incomplete, or missing `--index-url`/`--extra-index-url` args.
-4. The generated installer script will always include the complete Standard Template Structure with all required args.
+3. **Always use the Standard Template Structure** (see above) regardless of what the user's config shows.
+4. The generated installer script will always include the complete Standard Template Structure.
+5. **MCP_NAME must match the PyPI package name exactly**.
 
 **Cline config format (example - may vary):**
 ```json
@@ -144,18 +144,11 @@ The `args` array **MUST** always follow this structure:
     "type": "stdio",
     "command": "uvx",
     "args": [
-      "--from",
-      "backlog-mcp@latest",
-      "--index-url",
-      "https://test.pypi.org/simple/",
-      "--extra-index-url",
-      "https://pypi.org/simple/",
-      "backlog-mcp"
+      "backlog-mcp@latest"
     ]
   }
 }
 ```
-*Note: This example shows the complete Standard Template Structure. User configs may be missing `--index-url` or `--extra-index-url` - always use Standard Template Structure for PyPI packages.*
 
 **GitHub Copilot config format (example - may vary):**
 ```json
@@ -165,18 +158,11 @@ The `args` array **MUST** always follow this structure:
     "timeout": 60000,
     "command": "uvx",
     "args": [
-      "--from",
-      "backlog-mcp@latest",
-      "--index-url",
-      "https://test.pypi.org/simple/",
-      "--extra-index-url",
-      "https://pypi.org/simple/",
-      "backlog-mcp"
+      "backlog-mcp@latest"
     ]
   }
 }
 ```
-*Note: This example shows the complete Standard Template Structure. User configs may be missing `--index-url` or `--extra-index-url` - always use Standard Template Structure for PyPI packages.*
 
 **Claude Code config format (example - may vary):**
 ```json
@@ -184,27 +170,18 @@ The `args` array **MUST** always follow this structure:
   "backlog-mcp": {
     "command": "uvx",
     "args": [
-      "--from",
-      "backlog-mcp@latest",
-      "--index-url",
-      "https://test.pypi.org/simple/",
-      "--extra-index-url",
-      "https://pypi.org/simple/",
-      "backlog-mcp"
+      "backlog-mcp@latest"
     ]
   }
 }
 ```
-*Note: This example shows the complete Standard Template Structure. User configs may be missing `--index-url` or `--extra-index-url` - always use Standard Template Structure for PyPI packages.*
 
 ### Example Output
 
 The generated script will:
 - Ask which agent (Cline/Copilot/Claude Code)
 - Check if "backlog-mcp" already exists
-- Prompt for BACKLOG_API_KEY (with default from config)
-- Prompt for BACKLOG_DOMAIN (with default from config)
-- Prompt for USER_ID (with default from config)
+- Prompt for environment variables (if needed)
 - Write the configuration to the appropriate file
 
 ---
@@ -910,7 +887,7 @@ fi
 
 | Placeholder | Description | Example |
 |------------|-------------|---------|
-| `{{MCP_NAME}}` | The MCP server identifier (key in JSON) | `backlog-mcp` |
+| `{{MCP_NAME}}` | The MCP server identifier (key in JSON) - **must match PyPI package name exactly** | `backlog-mcp` |
 | `{{MCP_DISPLAY_NAME}}` | Human-readable name for prompts (used in banner) | `Backlog MCP` |
 | `{{COMMAND}}` | Command to run | `uvx` |
 | `{{ARGS}}` | Array of command arguments | See example below |
@@ -932,10 +909,18 @@ Extract from the JSON key:
 }
 ```
 
+**CRITICAL**: `{{MCP_NAME}}` **must match the PyPI package name exactly** for uvx to install correctly.
+
+**Examples:**
+- If PyPI package is `backlog-mcp` → `{{MCP_NAME}}` = `backlog-mcp`
+- If PyPI package is `mcp-server-sqlite` → `{{MCP_NAME}}` = `mcp-server-sqlite`
+- If PyPI package is `agent-coding-standards-mcp` → `{{MCP_NAME}}` = `agent-coding-standards-mcp`
+
 #### 2. `{{MCP_DISPLAY_NAME}}`
 Create a human-readable name:
 - `backlog-mcp` → `Backlog MCP`
 - `agent-coding-standards-mcp` → `Agent Coding Standards MCP`
+- `mcp-server-sqlite` → `MCP Server SQLite`
 
 #### 3. `{{COMMAND}}`
 Usually `uvx`, but check the config:
@@ -945,24 +930,28 @@ Usually `uvx`, but check the config:
 
 #### 4. `{{ARGS}}`
 
-**ALWAYS use the Standard Template Structure** (see "Standard Template Structure" section above). This template is for PyPI packages only.
+**Always use the Standard Template Structure:**
 
-Use this format:
 ```bash
-"--from" "{{PACKAGE_NAME}}@latest" "--index-url" "https://test.pypi.org/simple/" "--extra-index-url" "https://pypi.org/simple/" "{{MCP_NAME}}" "ENV_START"
+"{{MCP_NAME}}@latest" "ENV_START"
 ```
 
 **Placeholders:**
-- Replace `{{PACKAGE_NAME}}` with the actual PyPI package name (e.g., `backlog-mcp`)
-- Replace `{{MCP_NAME}}` with the MCP server identifier (usually same as package name, e.g., `backlog-mcp`)
+- Replace `{{MCP_NAME}}` with the MCP server identifier (e.g., `backlog-mcp`)
+- **CRITICAL**: `{{MCP_NAME}}` must match the PyPI package name exactly
 
 **Important:** 
 - Always append `"ENV_START"` as a marker after all args, before the env vars.
-- The `--index-url` and `--extra-index-url` arguments are **mandatory** and must always be included.
+- The `ENV_START` marker is used by the Python script to separate args from env vars.
 
 **Example (backlog-mcp):**
 ```bash
-"--from" "backlog-mcp@latest" "--index-url" "https://test.pypi.org/simple/" "--extra-index-url" "https://pypi.org/simple/" "backlog-mcp" "ENV_START"
+"backlog-mcp@latest" "ENV_START"
+```
+
+**Example (mcp-server-sqlite):**
+```bash
+"mcp-server-sqlite@latest" "ENV_START"
 ```
 
 #### 5. `{{ENV_VAR_SECTION}}` and `{{ENV_VAR_PROMPTS}}`
@@ -1088,7 +1077,7 @@ For Claude Code, always set:
 
 ## Complete Example: backlog-mcp
 
-This example demonstrates generating an installer script for a PyPI-published MCP server (`backlog-mcp`). The generated script will always use the **Standard Template Structure** for args.
+This example demonstrates generating an installer script for a PyPI-published MCP server (`backlog-mcp`).
 
 ### Input Configuration
 
@@ -1103,29 +1092,23 @@ This example demonstrates generating an installer script for a PyPI-published MC
     "type": "stdio",
     "command": "uvx",
     "args": [
-      "--from",
-      "backlog-mcp@latest",
-      "--index-url",
-      "https://test.pypi.org/simple/",
-      "--extra-index-url",
-      "https://pypi.org/simple/",
-      "backlog-mcp"
+      "backlog-mcp@latest"
     ]
   }
 }
 ```
 
-**Note**: The generated installer script will always use the complete Standard Template Structure with all required args, regardless of what the user's config shows.
+**Important**: The MCP name (`backlog-mcp`) matches the PyPI package name (`backlog-mcp`). This is required for uvx to work correctly.
 
 The LLM must ask the user about environment variables separately.
 
 ### Generated Placeholder Values
 
 ```bash
-MCP_NAME="backlog-mcp"
+MCP_NAME="backlog-mcp"  # Must match PyPI package name
 MCP_DISPLAY_NAME="Backlog MCP"
 COMMAND="uvx"
-ARGS="--from" "backlog-mcp@latest" "--index-url" "https://test.pypi.org/simple/" "--extra-index-url" "https://pypi.org/simple/" "backlog-mcp" "ENV_START"
+ARGS="backlog-mcp@latest" "ENV_START"  # MCP_NAME matches package name
 HAS_AUTO_APPROVE="true"
 HAS_DISABLED="true"
 HAS_TIMEOUT="true"
@@ -1201,10 +1184,10 @@ echo ""
 **Using Standard Template Structure:**
 
 ```bash
-"--from" "backlog-mcp@latest" "--index-url" "https://test.pypi.org/simple/" "--extra-index-url" "https://pypi.org/simple/" "backlog-mcp" "ENV_START"
+"backlog-mcp@latest" "ENV_START"
 ```
 
-**Note**: This always uses the Standard Template Structure with all required args (`--index-url` and `--extra-index-url` are mandatory).
+**Note**: `backlog-mcp` matches the PyPI package name exactly.
 
 ### Generated ENV_VAR_VALUES
 
@@ -1226,7 +1209,8 @@ When generating a script from this template:
 
 - [ ] Parse the MCP config JSON (if provided) or use template structure
 - [ ] Extract MCP name from the key
-- [ ] Extract command and args: Always use **Standard Template Structure** for args, include `--from`, `{{PACKAGE_NAME}}@latest`, `--index-url`, `--extra-index-url`, and `{{MCP_NAME}}`
+- [ ] **VERIFY**: MCP_NAME matches the PyPI package name exactly
+- [ ] Extract command and args: Always use **Standard Template Structure** for args
 - [ ] **ASK USER about env vars**: Does the MCP server need environment variables?
 - [ ] **For each env var needed**: Ask user if it's Fixed (cố định) or Variable (tùy biến)
   - If **Fixed**: Get value from user and hardcode in script
@@ -1242,30 +1226,34 @@ When generating a script from this template:
 
 ## Notes
 
-1. **Banner ASCII Art**: The banner is always the same ASCII art from `install-mcp.sh`. Only the `{{MCP_DISPLAY_NAME}}` changes in the banner.
+1. **Package Name Matching**: **CRITICAL** - The `{{MCP_NAME}}` must match the PyPI package name exactly for uvx to install correctly. For example:
+   - If PyPI package is `backlog-mcp` → MCP_NAME must be `backlog-mcp`
+   - If PyPI package is `mcp-server-sqlite` → MCP_NAME must be `mcp-server-sqlite`
+   - If PyPI package is `agent-coding-standards-mcp` → MCP_NAME must be `agent-coding-standards-mcp`
 
-2. **Sensitive Value Detection**: The template automatically detects sensitive values by checking if the env var name contains: `TOKEN`, `PASSWORD`, `KEY`, `SECRET`, or `API_KEY` (case-insensitive).
+2. **Banner ASCII Art**: The banner is always the same ASCII art from `install-mcp.sh`. Only the `{{MCP_DISPLAY_NAME}}` changes in the banner.
 
-3. **Agent-Specific Behavior**: 
+3. **Sensitive Value Detection**: The template automatically detects sensitive values by checking if the env var name contains: `TOKEN`, `PASSWORD`, `KEY`, `SECRET`, or `API_KEY` (case-insensitive).
+
+4. **Agent-Specific Behavior**: 
    - **Cline**: Supports all optional fields. Timeout uses **seconds** (e.g., `60` = 60 seconds)
    - **GitHub Copilot**: Doesn't support `autoApprove` or `disabled`. Timeout uses **milliseconds** (e.g., `60000` = 60 seconds). The Python script automatically converts seconds to milliseconds.
    - **Claude Code**: Doesn't support any optional fields (no timeout)
 
-4. **Workflow**: The template file is typically placed in a PyPI project repository (90% of use cases). When generating an installer script, the LLM should parse the config structure and ask the user about environment variables.
+5. **Workflow**: The template file is typically placed in a PyPI project repository (90% of use cases). When generating an installer script, the LLM should parse the config structure and ask the user about environment variables.
 
-5. **Config Format**: MCP configurations from Cline, GitHub Copilot, or Claude Code do NOT include an `env` field by default. The LLM must ask the user about environment variables separately.
+6. **Config Format**: MCP configurations from Cline, GitHub Copilot, or Claude Code do NOT include an `env` field by default. The LLM must ask the user about environment variables separately.
 
-6. **Environment Variables**: There are two types of env vars:
+7. **Environment Variables**: There are two types of env vars:
    - **Fixed (Cố định)**: User provides the value when LLM asks → LLM hardcodes it into the script (no prompt in script). Use this for static values that don't change.
    - **Variable (Tùy biến)**: LLM generates prompt code in the script to ask user when running. Use this for values that vary per installation.
 
-7. **Error Handling**: The script includes comprehensive error handling for:
+8. **Error Handling**: The script includes comprehensive error handling for:
    - Missing system requirements
    - Invalid JSON in config files
    - Existing MCP configurations
    - Missing environment variables
 
-8. **JSON Comments**: The script handles JSON files with comments (both `//` and `/* */` style) by stripping them before parsing.
-
-9. **Important Bug Fix**: The `strip_json_comments` function uses `enumerate(lines)` instead of `lines.index(line)` to get the current line index. This prevents the `"'...' is not in list"` error that occurs when a modified line (after stripping comments) cannot be found in the original list. Always use `line_idx` from `enumerate()` when accessing `lines[line_idx+1:]` to check for trailing commas.
+9. **JSON Comments**: The script handles JSON files with comments (both `//` and `/* */` style) by stripping them before parsing.
 
+10. **Important Bug Fix**: The `strip_json_comments` function uses `enumerate(lines)` instead of `lines.index(line)` to get the current line index. This prevents the `"'...' is not in list"` error that occurs when a modified line (after stripping comments) cannot be found in the original list. Always use `line_idx` from `enumerate()` when accessing `lines[line_idx+1:]` to check for trailing commas.

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "backlog-mcp"
-version = "1.0.1"
+version = "1.0.3"
 description = "A Model Context Protocol (MCP) server for Backlog project management integration"
 authors = [{name = "BaoNguyen", email = "baonguyen@teqnological.asia"}]
 readme = "README.md"

{backlog_mcp-1.0.1 → backlog_mcp-1.0.3}/uv.lock

@@ -1,5 +1,5 @@
 version = 1
-revision = 2
+revision = 3
 requires-python = "==3.13.*"
 
 [[package]]
@@ -34,7 +34,7 @@ wheels = [
 
 [[package]]
 name = "backlog-mcp"
-version = "0.0.10"
+version = "1.0.2"
 source = { editable = "." }
 dependencies = [
     { name = "httpx" },

backlog_mcp-1.0.1/app/tools/get_user_issue_list.py

@@ -1,70 +0,0 @@
-from app.utils.di import create_backlog_context
-from app.utils.ultils import get_user_task
-
-from app.server_settings import settings
-
-
-async def get_user_issue_list(
-    project_ids: list[int] | None = None,
-    assignee_ids: list[int] | None = None,
-    status_ids: list[int] | None = None,
-    milestone_ids: list[int] | None = None,
-    parent_issue_ids: list[int] | None = None,
-    created_since: str | None = None,
-    created_until: str | None = None,
-    updated_since: str | None = None,
-    updated_until: str | None = None,
-    start_date_since: str | None = None,
-    start_date_until: str | None = None,
-    due_date_since: str | None = None,
-    due_date_until: str | None = None,
-):
-    """
-    Retrieves a filtered list of issues from Backlog for the users.
-
-    Args:
-        project_ids (list[int], optional): List of project IDs to filter issues.
-        assignee_ids (list[int], optional): List of assignee IDs to filter issues (defaults to current user).
-        status_ids (list[int], optional): List of status IDs to filter issues (defaults to all non-closed statuses).
-        milestone_ids (list[int], optional): List of milestone IDs to filter issues.
-        parent_issue_ids (list[int], optional): List of parent issue IDs to filter issues.
-
-        created_since (str, optional): Created since (YYYY-MM-DD).
-        created_until (str, optional): Created until (YYYY-MM-DD).
-
-        updated_since (str, optional): Updated since (YYYY-MM-DD).
-        updated_until (str, optional): Updated until (YYYY-MM-DD).
-
-        start_date_since (str, optional): Start Date since (YYYY-MM-DD).
-        start_date_until (str, optional): Start Date until (YYYY-MM-DD).
-
-        due_date_since (str, optional): Due Date since (YYYY-MM-DD).
-        due_date_until (str, optional): Due Date until (YYYY-MM-DD).
-    """
-
-    try:
-        ctx = create_backlog_context()
-
-        if assignee_ids is None:
-            assignee_ids = [settings.USER_ID]
-
-        issue_list = await get_user_task(
-            backlog_domain=ctx.backlog_domain,
-            api_key=ctx.api_key,
-            project_ids=project_ids,
-            assignee_ids=assignee_ids,
-            status_ids=status_ids,
-            milestone_ids=milestone_ids,
-            parent_issue_ids=parent_issue_ids,
-            created_since=created_since,
-            created_until=created_until,
-            updated_since=updated_since,
-            updated_until=updated_until,
-            start_date_since=start_date_since,
-            start_date_until=start_date_until,
-            due_date_since=due_date_since,
-            due_date_until=due_date_until
-        )
-        return issue_list
-    except Exception as e:
-        raise e