@mohammadhprp/system-prompt 0.12.1 → 0.12.3

package/framework/mcps/gitlab-mcp/capabilities.md

@@ -1,216 +0,0 @@
-# GitLab MCP Capabilities
-
-## What It Can Do
-
-117+ tools across projects, merge requests, issues, pipelines, wiki, milestones, labels, and more.
-
-### Merge Requests
-
-| Tool | Description |
-| --- | --- |
-| `list_merge_requests` | List merge requests with filtering |
-| `get_merge_request` | Get merge request details |
-| `create_merge_request` | Create a new merge request |
-| `update_merge_request` | Update a merge request |
-| `merge_merge_request` | Merge a merge request |
-| `approve_merge_request` | Approve a merge request |
-| `unapprove_merge_request` | Unapprove a merge request |
-| `get_merge_request_approval_state` | Get approval details including approvers |
-| `get_merge_request_diffs` | Get the changes/diffs of a merge request |
-| `list_merge_request_diffs` | List diffs with pagination |
-| `get_merge_request_conflicts` | Get merge request conflicts |
-| `list_merge_request_changed_files` | List changed file paths (without diff) |
-| `get_merge_request_file_diff` | Get diffs for specific files |
-| `list_merge_request_versions` | List all versions of a merge request |
-| `get_merge_request_version` | Get a specific version |
-| `get_branch_diffs` | Get diffs between two branches or commits |
-| `mr_discussions` | List discussion items for a merge request |
-| `resolve_merge_request_thread` | Resolve a thread |
-| `create_merge_request_thread` | Create a new thread |
-| `create_merge_request_note` | Add a note to an existing thread |
-| `create_merge_request_discussion_note` | Add a discussion note |
-| `update_merge_request_note` | Modify a merge request note |
-| `update_merge_request_discussion_note` | Update a discussion note |
-| `delete_merge_request_note` | Delete a merge request note |
-| `delete_merge_request_discussion_note` | Delete a discussion note |
-| `get_merge_request_note` | Get a specific note |
-| `get_merge_request_notes` | List notes for a merge request |
-| `create_note` | Create a comment on an issue or MR |
-| `get_draft_note` | Get a single draft note |
-| `list_draft_notes` | List draft notes |
-| `create_draft_note` | Create a draft note |
-| `update_draft_note` | Update a draft note |
-| `delete_draft_note` | Delete a draft note |
-| `publish_draft_note` | Publish a single draft note |
-| `bulk_publish_draft_notes` | Publish all draft notes |
-
-### Issues
-
-| Tool | Description |
-| --- | --- |
-| `list_issues` | List issues with filtering |
-| `my_issues` | List issues assigned to the current user |
-| `get_issue` | Get issue details |
-| `create_issue` | Create a new issue |
-| `update_issue` | Update an issue |
-| `update_issue_description_patch` | Apply a patch to an issue description |
-| `delete_issue` | Delete an issue |
-| `create_issue_note` | Add a note to an issue thread |
-| `update_issue_note` | Modify an issue thread note |
-| `list_issue_discussions` | List discussions for an issue |
-| `list_issue_links` | List issue links |
-| `get_issue_link` | Get a specific issue link |
-| `create_issue_link` | Link two issues |
-| `delete_issue_link` | Delete an issue link |
-
-### Projects & Repositories
-
-| Tool | Description |
-| --- | --- |
-| `search_repositories` | Search for GitLab projects |
-| `create_repository` | Create a new GitLab project |
-| `get_project` | Get project details |
-| `list_projects` | List accessible projects |
-| `list_project_members` | List project members |
-| `fork_repository` | Fork a project |
-| `list_group_projects` | List projects in a group |
-| `list_namespaces` | List available namespaces |
-| `get_namespace` | Get namespace details |
-| `verify_namespace` | Verify a namespace path exists |
-| `create_group` | Create a new group or subgroup |
-| `list_group_iterations` | List group iterations |
-
-### Files & Commits
-
-| Tool | Description |
-| --- | --- |
-| `get_file_contents` | Get file or directory contents |
-| `create_or_update_file` | Create or update a single file |
-| `push_files` | Push multiple files in a single commit |
-| `create_branch` | Create a new branch |
-| `get_repository_tree` | List repository files and directories |
-| `list_commits` | List commits with filtering |
-| `get_commit` | Get commit details |
-| `get_commit_diff` | Get commit changes/diffs |
-
-### CI/CD Pipelines
-
-| Tool | Description |
-| --- | --- |
-| `list_pipelines` | List pipelines with filtering |
-| `get_pipeline` | Get pipeline details |
-| `create_pipeline` | Create a pipeline for a branch or tag |
-| `retry_pipeline` | Retry a failed or canceled pipeline |
-| `cancel_pipeline` | Cancel a running pipeline |
-| `list_pipeline_jobs` | List all jobs in a pipeline |
-| `list_pipeline_trigger_jobs` | List trigger jobs (bridges) |
-| `get_pipeline_job` | Get job details |
-| `get_pipeline_job_output` | Get job output/trace with pagination |
-| `play_pipeline_job` | Run a manual pipeline job |
-| `retry_pipeline_job` | Retry a failed job |
-| `cancel_pipeline_job` | Cancel a running job |
-| `validate_ci_lint` | Validate CI/CD YAML content |
-| `validate_project_ci_lint` | Validate existing `.gitlab-ci.yml` |
-| `list_job_artifacts` | List artifact files in a job |
-| `download_job_artifacts` | Download artifact archive (zip) |
-| `get_job_artifact_file` | Get content of a single artifact file |
-| `list_deployments` | List deployments |
-| `get_deployment` | Get deployment details |
-| `list_environments` | List environments |
-| `get_environment` | Get environment details |
-
-### Wiki
-
-| Tool | Description |
-| --- | --- |
-| `list_wiki_pages` | List project wiki pages |
-| `get_wiki_page` | Get wiki page details |
-| `create_wiki_page` | Create a new wiki page |
-| `update_wiki_page` | Update a wiki page |
-| `delete_wiki_page` | Delete a wiki page |
-| `list_group_wiki_pages` | List group wiki pages |
-| `get_group_wiki_page` | Get group wiki page details |
-| `create_group_wiki_page` | Create a group wiki page |
-| `update_group_wiki_page` | Update a group wiki page |
-| `delete_group_wiki_page` | Delete a group wiki page |
-
-### Milestones
-
-| Tool | Description |
-| --- | --- |
-| `list_milestones` | List milestones with filtering |
-| `get_milestone` | Get milestone details |
-| `create_milestone` | Create a new milestone |
-| `edit_milestone` | Edit an existing milestone |
-| `delete_milestone` | Delete a milestone |
-| `get_milestone_issue` | Get issues for a milestone |
-| `get_milestone_merge_requests` | Get MRs for a milestone |
-| `get_milestone_burndown_events` | Get burndown events |
-| `promote_milestone` | Promote a milestone |
-
-### Labels & To-Dos
-
-| Tool | Description |
-| --- | --- |
-| `list_labels` | List project labels |
-| `get_label` | Get a single label |
-| `create_label` | Create a new label |
-| `update_label` | Update an existing label |
-| `delete_label` | Delete a label |
-| `list_todos` | List to-do items |
-| `mark_todo_done` | Mark a to-do item as done |
-| `mark_all_todos_done` | Mark all to-do items as done |
-
-### Releases (not listed in README tools, but mentioned in features)
-
-The server may expose additional release and tag management tools depending on the installed version. Refer to the official [documentation](https://zereight.github.io/gitlab-mcp/) for the full tool list.
-
-## What It Cannot Do
-
-- It cannot operate without a GitLab account and API token or OAuth credentials.
-- It cannot access GitLab features outside the authenticated user's permissions.
-- It does not support SSE transport when using `REMOTE_AUTHORIZATION` mode (Streamable HTTP required).
-- It cannot safely infer production intent; agents still need explicit instructions before destructive operations.
-- Read-only mode (`GITLAB_PERMISSION_MODE=readonly`) blocks all write, update, and delete tools but does not prevent the agent from reading sensitive project data that the token has access to.
-
-## Best Practices
-
-- Use a Personal Access Token with the minimum required scopes (`read_api` for read-only workflows, `api` for write workflows).
-- Use `GITLAB_PERMISSION_MODE=readonly` or `modify` to restrict agent capabilities.
-- Use `GITLAB_TOOLSETS` to enable only the tool groups needed (e.g., `wiki,milestones,pipelines`).
-- Use `GITLAB_TOOLS` allow-list to enable individual tools, and `GITLAB_DENIED_TOOLS_REGEX` to block by pattern.
-- Prefer OAuth2 over PAT for better security in desktop workflows.
-- For multi-user deployments, use `REMOTE_AUTHORIZATION` so each caller provides their own token.
-- Use `list_merge_request_changed_files` first, then `get_merge_request_file_diff` on selected files, to reduce token usage during code review.
-- Validate CI/CD changes with `validate_ci_lint` before committing.
-
-## Common Workflows
-
-### Review a merge request
-
-1. Call `list_merge_request_changed_files` to see which files changed.
-2. Call `get_merge_request_file_diff` on 3-5 files at a time to review diffs.
-3. Call `get_merge_request_approval_state` to check approvers.
-4. Use `create_merge_request_thread` or `create_note` to leave feedback.
-5. Call `approve_merge_request` and `merge_merge_request` when ready.
-
-### Investigate a pipeline failure
-
-1. Call `list_pipelines` to find the failed pipeline.
-2. Call `list_pipeline_jobs` to see which jobs failed.
-3. Call `get_pipeline_job_output` to read the failing job's logs.
-4. Use the logs to diagnose the issue and propose a fix.
-
-### Manage issues
-
-1. Call `list_issues` or `my_issues` to see open issues.
-2. Call `get_issue` to read details of a specific issue.
-3. Call `create_issue_note` to comment or request clarification.
-4. Call `update_issue` to change status, assignee, or labels.
-
-### Browse and edit repository files
-
-1. Call `get_repository_tree` to list files in a directory.
-2. Call `get_file_contents` to read specific files.
-3. Call `create_or_update_file` or `push_files` to make changes.
-4. Call `create_branch` and `create_merge_request` to propose changes.

package/framework/mcps/gitlab-mcp/configs/.env.example

@@ -1,2 +0,0 @@
-GITLAB_API_URL=
-GITLAB_PERSONAL_ACCESS_TOKEN=

package/framework/mcps/gitlab-mcp/configs/opencode.json

@@ -1,13 +0,0 @@
-{
-  "mcp": {
-    "gitlab": {
-        "type": "local",
-        "enabled": true,
-        "command": ["bun", "x", "@zereight/mcp-gitlab"],
-        "environment": {
-            "GITLAB_PERSONAL_ACCESS_TOKEN": "{env:GITLAB_PERSONAL_ACCESS_TOKEN}",
-            "GITLAB_API_URL": "{env:GITLAB_API_URL}"
-        }
-    }
-  }
-}

package/framework/mcps/gitlab-mcp/install.md

@@ -1,99 +0,0 @@
-# GitLab MCP Installation
-
-## Requirements
-
-- Node.js >= 18 and npm available on `PATH`, or Homebrew.
-- A GitLab account with API access.
-- A GitLab Personal Access Token with `api` scope (or `read_api` for read-only mode).
-- An MCP-compatible AI client.
-
-## Authentication
-
-The server supports four authentication methods:
-
-| Method | Best for |
-| --- | --- |
-| Personal Access Token (PAT) | Simplest local setup |
-| OAuth2 — Local Browser | Better security for desktop use |
-| OAuth2 — MCP Proxy | Remote deployments (Claude.ai, etc.) |
-| Remote Authorization | Multi-user deployments with per-request tokens |
-
-## Installation
-
-Install globally via npm or Homebrew:
-
-```bash
-npm install -g @zereight/mcp-gitlab
-```
-
-Or with Homebrew:
-
-```bash
-brew install zereight/gitlab-mcp/zereight-mcp-gitlab
-```
-
-No global install? Use `npx` pinned to a specific version:
-
-```bash
-npx -y @zereight/mcp-gitlab@latest
-```
-
-## Configuration
-
-| Field | Value |
-| --- | --- |
-| Server name | `gitlab` |
-| Command | `zereight-mcp-gitlab` |
-| Env | `GITLAB_PERSONAL_ACCESS_TOKEN`, `GITLAB_API_URL` |
-| Alt command (no global install) | `npx` with args `-y`, `@zereight/mcp-gitlab@latest` |
-| CLI args | `--token`, `--api-url`, `--permission-mode` |
-
-### Config file examples
-
-Use the examples in [`configs/`](./configs/) as client-specific starting points:
-
-| Client | Example | Typical location |
-| --- | --- | --- |
-| OpenCode | [`configs/opencode.json`](./configs/opencode.json) | OpenCode MCP configuration. |
-
-### OpenCode
-
-Copy [`configs/opencode.json`](./configs/opencode.json) into your OpenCode project root or user config directory, replace the placeholder token and API URL, and restart the OpenCode agent.
-
-## Verification
-
-Run the MCP server command directly:
-
-```bash
-zereight-mcp-gitlab
-```
-
-Then verify from your AI client:
-
-- The `gitlab` MCP server is listed.
-- The server starts without errors.
-- Tools are visible to the agent.
-
-Recommended first prompt:
-
-```
-List my GitLab projects and show me recent merge requests.
-```
-
-## Updating
-
-```bash
-npm update -g @zereight/mcp-gitlab
-```
-
-## Uninstalling
-
-1. Remove the MCP entry from AI client configuration files.
-2. Uninstall the package: `npm uninstall -g @zereight/mcp-gitlab`.
-
-## Common Issues
-
-- **Server does not start**: run `zereight-mcp-gitlab` manually and fix the first error shown. Ensure Node.js >= 18 is installed.
-- **Authentication errors**: confirm the PAT has the correct scopes and the API URL is `https://gitlab.com/api/v4` (not the web URL).
-- **Client cannot find the server**: use the absolute path from `which zereight-mcp-gitlab`, or use `npx` as the command instead.
-- **Wrong API URL**: use `https://gitlab.com/api/v4` for GitLab SaaS, or `https://your-instance/api/v4` for self-hosted.

package/framework/mcps/gitlab-mcp/troubleshooting.md

@@ -1,116 +0,0 @@
-# GitLab MCP Troubleshooting
-
-## Server won't start
-
-**Problem**
-
-The AI client reports that `gitlab` failed to start.
-
-**Cause**
-
-The client cannot run `zereight-mcp-gitlab`, Node.js is not installed, or the npm package is not installed globally.
-
-**Solution**
-
-- Run `zereight-mcp-gitlab` manually to verify the server starts.
-- Check Node.js is installed: `node --version` (requires >= 18).
-- Run `npm install -g @zereight/mcp-gitlab` to install globally.
-- If no global install, use `command: "npx"` with `args: ["-y", "@zereight/mcp-gitlab"]` instead.
-
-## Authentication errors
-
-**Problem**
-
-The server starts but returns authentication errors on tool calls.
-
-**Cause**
-
-The Personal Access Token is missing, expired, or has insufficient scopes.
-
-**Solution**
-
-- Verify the token is set in `GITLAB_PERSONAL_ACCESS_TOKEN` or passed via `--token`.
-- Confirm the token has the required scopes (`api` for full access, `read_api` for read-only).
-- Generate a new token in GitLab: **Settings → Access Tokens → Personal Access Tokens**.
-- Confirm the API URL is correct: `https://gitlab.com/api/v4` (SaaS) or `https://your-instance/api/v4` (self-hosted).
-
-## Configuration errors
-
-**Problem**
-
-The MCP server is not listed, or the client ignores the config file.
-
-**Cause**
-
-The config file is in the wrong location, the JSON is invalid, or the client expects a different configuration wrapper.
-
-**Solution**
-
-- Validate the JSON with `python -m json.tool <file>` or another JSON parser.
-- Confirm the client-specific config location in the client's documentation.
-- Keep the server name as `gitlab`.
-- Ensure environment variables are set correctly in the config.
-
-## Permission errors
-
-**Problem**
-
-Tools return 403 Forbidden or insufficient permissions.
-
-**Cause**
-
-The authenticated user does not have the required GitLab project or group permissions.
-
-**Solution**
-
-- Verify the user has at least Developer role in the target project or group.
-- Check if the project is in a subgroup that inherits different permissions.
-- Use `list_projects` to confirm which projects the token can access.
-
-## Rate limiting
-
-**Problem**
-
-Tools return 429 Too Many Requests errors.
-
-**Cause**
-
-GitLab API rate limits have been exceeded.
-
-**Solution**
-
-- Reduce the frequency of tool calls.
-- For self-hosted GitLab, check `gitlab.rb` rate limit settings.
-- Wait for the rate limit window to reset before retrying.
-
-## Version mismatch
-
-**Problem**
-
-Some tools are missing or behave differently than documented.
-
-**Cause**
-
-The installed npm package version is outdated.
-
-**Solution**
-
-- Update to the latest version: `npm update -g @zereight/mcp-gitlab`.
-- Check the installed version: `npm list -g @zereight/mcp-gitlab`.
-- Refer to the [CHANGELOG](https://github.com/zereight/gitlab-mcp/blob/main/CHANGELOG.md) for breaking changes.
-
-## Read-only mode blocking writes
-
-**Problem**
-
-Write tools return errors when `GITLAB_PERMISSION_MODE=readonly`.
-
-**Cause**
-
-Read-only mode explicitly blocks all create, update, and delete operations.
-
-**Solution**
-
-- Set `GITLAB_PERMISSION_MODE=modify` to allow updates while blocking deletes.
-- Set `GITLAB_PERMISSION_MODE=full` for unrestricted access.
-- Use `GITLAB_TOOLS` allow-list to enable specific write tools in read-only mode.

package/framework/mcps/jira-mcp/README.md

@@ -1,52 +0,0 @@
-# Jira MCP
-
-## Overview
-
-Jira MCP is a Model Context Protocol (MCP) server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It provides tools for creating, reading, updating, and deleting issues, searching with JQL, managing comments and assignments, and inspecting projects.
-
-Official source:
-
-- [GitHub: edrich13/mcp-jira-server](https://github.com/edrich13/mcp-jira-server)
-
-## Features
-
-- Personal Access Token authentication for self-hosted Jira.
-- Create, read, update, and delete Jira issues.
-- Search issues using JQL (Jira Query Language).
-- Add and view comments.
-- Manage issue assignments.
-- List projects and issue types.
-- Transition issues between statuses.
-- Get current user information.
-
-## Supported AI Clients
-
-Jira MCP works with any MCP-compatible AI client. The server is started via `npx` and communicates over stdio.
-
-- OpenCode
-
-## When to Use
-
-Use Jira MCP when an AI coding agent needs to interact with a self-hosted Jira instance.
-
-Good fits:
-
-- Creating and updating Jira issues from an AI agent.
-- Searching for issues with JQL queries.
-- Adding comments and managing issue assignments.
-- Inspecting project metadata and issue types.
-- Tracking work and status transitions.
-
-Avoid using it with Jira Cloud (SaaS) — this server is designed for self-hosted Jira instances only.
-
-## Requirements
-
-- Node.js 18 or higher available on `PATH`.
-- A self-hosted Jira instance (e.g., `https://jira.domain.com`).
-- A Jira Personal Access Token with appropriate permissions.
-
-## Related Skills
-
-Relevant skills in this repository:
-
-- [`backend-best-practices`](../../skills/backend-best-practices/SKILL.md): backend best practices for debugging and testing.

package/framework/mcps/jira-mcp/capabilities.md

@@ -1,79 +0,0 @@
-# Jira MCP Capabilities
-
-## What It Can Do
-
-12 tools for interacting with self-hosted Jira instances.
-
-### Issues
-
-| Tool | Description |
-| --- | --- |
-| `jira_get_issue` | Get details of a specific issue by key (e.g. "PROJ-123") |
-| `jira_search_issues` | Search for issues using JQL with optional max results |
-| `jira_create_issue` | Create a new issue with project, summary, type, description, priority, assignee, labels, components, and custom fields |
-| `jira_update_issue` | Update an existing issue — summary, description, assignee, priority, labels, status, and custom fields |
-| `jira_delete_issue` | Delete an issue permanently |
-| `jira_assign_issue` | Assign an issue to a user |
-
-### Comments
-
-| Tool | Description |
-| --- | --- |
-| `jira_add_comment` | Add a comment to an issue |
-| `jira_get_comments` | Get all comments from an issue |
-
-### Projects
-
-| Tool | Description |
-| --- | --- |
-| `jira_get_projects` | List all available projects |
-| `jira_get_project` | Get details of a specific project |
-| `jira_get_issue_types` | Get available issue types for a project |
-
-### User
-
-| Tool | Description |
-| --- | --- |
-| `jira_get_current_user` | Get information about the currently authenticated user |
-
-## What It Cannot Do
-
-- It does not work with Jira Cloud (SaaS) — designed for self-hosted instances only.
-- It cannot authenticate with OAuth, API tokens, or cookie-based auth — PAT only.
-- It cannot create, update, or delete Jira projects.
-- It cannot manage Jira users, groups, or permissions.
-- It cannot access Jira boards, sprints, or agile features.
-- It cannot attach files to issues.
-- It cannot operate without a valid PAT and accessible Jira instance.
-
-## Best Practices
-
-- Never commit your PAT to version control. Use environment variables or client config files with restricted permissions.
-- Use tokens with minimal required permissions.
-- Set expiration dates for tokens and rotate them regularly.
-- Use `jira_get_issue_types` before creating issues to confirm valid types for the project.
-- Use `jira_get_current_user` first to verify authentication is working.
-- Use JQL with specific project keys to scope searches and reduce response size.
-- For Jira instances behind SSO proxies, set `JIRA_USER_AGENT` to a whitelisted value.
-
-## Common Workflows
-
-### Find and update issues
-
-1. Call `jira_search_issues` with a JQL query to find relevant issues.
-2. Call `jira_get_issue` on a specific key to read full details.
-3. Call `jira_update_issue` to change status, assignee, or priority.
-4. Call `jira_add_comment` to leave a note about the change.
-
-### Create a new issue
-
-1. Call `jira_get_projects` to list available projects.
-2. Call `jira_get_issue_types` for the target project.
-3. Call `jira_create_issue` with project key, summary, issue type, and optional fields.
-4. Call `jira_assign_issue` to assign it to a team member.
-
-### Track work progress
-
-1. Call `jira_search_issues` with `assignee = currentUser() AND status != Done`.
-2. Call `jira_get_issue` on each key to review details.
-3. Call `jira_update_issue` to transition statuses as work progresses.

package/framework/mcps/jira-mcp/configs/.env.example

@@ -1,2 +0,0 @@
-JIRA_BASE_URL=
-JIRA_PAT=

package/framework/mcps/jira-mcp/configs/opencode.json

@@ -1,13 +0,0 @@
-{
-  "mcp": {
-    "jira": {
-      "type": "local",
-      "enabled": true,
-      "command": ["npx", "-y", "mcp-jira-server"],
-      "environment": {
-        "JIRA_BASE_URL": "{env:JIRA_BASE_URL}",
-        "JIRA_PAT": "{env:JIRA_PAT}"
-      }
-    }
-  }
-}

package/framework/mcps/jira-mcp/install.md

@@ -1,94 +0,0 @@
-# Jira MCP Installation
-
-## Requirements
-
-- Node.js 18 or higher available on `PATH`.
-- A self-hosted Jira instance.
-- A Jira Personal Access Token.
-- An MCP-compatible AI client.
-
-## Creating a Personal Access Token
-
-1. Log in to your self-hosted Jira instance.
-2. Click your profile icon → **Profile** or **Account Settings**.
-3. Navigate to **Personal Access Tokens** or **Security**.
-4. Click **Create token**, give it a name, set an expiration date, and copy the token immediately.
-
-## Installation
-
-The server can be used directly with `npx` — no build step required.
-
-```bash
-npx -y mcp-jira-server
-```
-
-Or install globally:
-
-```bash
-npm install -g mcp-jira-server
-```
-
-## Configuration
-
-| Field | Value |
-| --- | --- |
-| Server name | `jira` |
-| Command | `npx` (or `mcp-jira-server` if installed globally) |
-| Args | `-y`, `mcp-jira-server` |
-| Env | `JIRA_BASE_URL`, `JIRA_PAT` |
-
-### Config file examples
-
-Use the examples in [`configs/`](./configs/) as client-specific starting points:
-
-| Client | Example | Typical location |
-| --- | --- | --- |
-| OpenCode | [`configs/opencode.json`](./configs/opencode.json) | OpenCode MCP configuration. |
-
-### OpenCode
-
-Copy [`configs/opencode.json`](./configs/opencode.json) into your OpenCode project root or user config directory, replace the placeholder URL and token, and restart the OpenCode agent.
-
-## Verification
-
-Run the MCP server command directly:
-
-```bash
-npx -y mcp-jira-server
-```
-
-Then verify from your AI client:
-
-- The `jira` MCP server is listed.
-- The server starts without errors.
-- Tools are visible to the agent.
-
-Recommended first prompt:
-
-```
-Get my current Jira user information
-```
-
-## Updating
-
-```bash
-npx -y mcp-jira-server@latest
-```
-
-Or update global install:
-
-```bash
-npm update -g mcp-jira-server
-```
-
-## Uninstalling
-
-1. Remove the MCP entry from AI client configuration files.
-2. Uninstall the package: `npm uninstall -g mcp-jira-server`.
-
-## Common Issues
-
-- **Server does not start**: run `npx -y mcp-jira-server` manually. Ensure Node.js >= 18 is installed.
-- **Authentication errors**: verify the PAT is valid and not expired. Confirm `JIRA_BASE_URL` has no trailing slash.
-- **Connection refused**: check if the Jira instance is accessible and the URL is correct.
-- **API requests redirect to SSO login**: your Jira may be behind a reverse proxy. Set `JIRA_USER_AGENT` to a whitelisted User-Agent string.