{"_id":"jira-mcp-scoped","_rev":"2-f17dd9d4f34a0e1a60c1d7d6a0901b20","name":"jira-mcp-scoped","dist-tags":{"latest":"1.0.1"},"versions":{"1.0.0":{"name":"jira-mcp-scoped","version":"1.0.0","keywords":["mcp","modelcontextprotocol","jira","atlassian","issue-tracking"],"author":{"name":"Michał Osadowski"},"license":"ISC","_id":"jira-mcp-scoped@1.0.0","maintainers":[{"name":"michalosadowski","email":"osadowskimichal@gmail.com"}],"homepage":"https://github.com/MichalOsadowski/jira-mcp#readme","bugs":{"url":"https://github.com/MichalOsadowski/jira-mcp/issues"},"bin":{"jira-mcp-scoped":"mcpOverStdio.js"},"dist":{"shasum":"b5a0466ec63e8aa53e251e75aec861bf172aba59","tarball":"https://registry.npmjs.org/jira-mcp-scoped/-/jira-mcp-scoped-1.0.0.tgz","fileCount":8,"integrity":"sha512-Z0WVkXEr/CQi0F7oqKLiJy1OiNgklDOeFroLnj8BZAiT5iFii85rh83TVnUzTZsHozMvnLX72FDGkSg/q/Fv/A==","signatures":[{"sig":"MEYCIQD4U2wCDjDc7eOLawkybomyRexLbd8kM8OfJKpQm39tRgIhANB6WEu1xmRR1J8dI90Urhf7q2nmLmmhivGzj38g9hrP","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":37095},"main":"mcpOverStdio.js","type":"module","engines":{"node":">=20"},"gitHead":"a09a323d1bf48bbd3437da42947b3c824b247081","scripts":{"test":"node --test","start":"node mcpOverStdio.js","start:http":"node mcpOverHttp.js"},"_npmUser":{"name":"michalosadowski","email":"osadowskimichal@gmail.com"},"overrides":{"minimatch":"^10.2.1"},"repository":{"url":"git+https://github.com/MichalOsadowski/jira-mcp.git","type":"git"},"_npmVersion":"11.17.0","description":"Project-scoped MCP server for Jira — issues, comments, sprints, transitions and attachments over the Jira REST API, narrowed to a single project instead of everything the account can access","directories":{},"_nodeVersion":"24.19.0","dependencies":{"zod":"^3.0.0","adf-to-md":"^1.2.1","marklassian":"^1.1.0","@modelcontextprotocol/sdk":"^1.0.0"},"_hasShrinkwrap":false,"devDependencies":{"semantic-release":"^25.0.9","@semantic-release/git":"^10.0.1","@semantic-release/changelog":"^6.0.3"},"_npmOperationalInternal":{"tmp":"tmp/jira-mcp-scoped_1.0.0_1786448658177_0.06694165660326035","host":"s3://npm-registry-packages-npm-production"}},"1.0.1":{"name":"jira-mcp-scoped","version":"1.0.1","description":"Project-scoped MCP server for Jira — issues, comments, sprints, transitions and attachments over the Jira REST API, narrowed to a single project instead of everything the account can access","type":"module","bin":{"jira-mcp-scoped":"mcpOverStdio.js"},"main":"mcpOverStdio.js","scripts":{"test":"node --test","start":"node mcpOverStdio.js","start:http":"node mcpOverHttp.js"},"repository":{"type":"git","url":"git+https://github.com/MichalOsadowski/jira-mcp.git"},"keywords":["mcp","modelcontextprotocol","jira","atlassian","issue-tracking"],"author":{"name":"Michał Osadowski"},"contributors":[{"name":"Henrik Holstad","url":"https://github.com/HenrikHolstad"}],"license":"ISC","engines":{"node":">=20"},"bugs":{"url":"https://github.com/MichalOsadowski/jira-mcp/issues"},"homepage":"https://github.com/MichalOsadowski/jira-mcp#readme","overrides":{"minimatch":"^10.2.1"},"dependencies":{"@modelcontextprotocol/sdk":"^1.0.0","adf-to-md":"^1.2.1","marklassian":"^1.1.0","zod":"^3.0.0"},"devDependencies":{"@semantic-release/changelog":"^6.0.3","@semantic-release/git":"^10.0.1","semantic-release":"^25.0.9"},"gitHead":"0425cfe3756461e92e15e14e26b9ce59f8e03d76","_id":"jira-mcp-scoped@1.0.1","_nodeVersion":"24.18.0","_npmVersion":"11.19.0","dist":{"integrity":"sha512-Grwd2GhBhhpVBiHhNT4vDF5Mmb0pyW8lBVD+JlTVXWCkwttAEgOmqQiL6Rr6mLXTgf6tRAaNozi3DiKMRwBLKw==","shasum":"3d8aff0b923bc219d1d34601c6372a6a16ca5be8","tarball":"https://registry.npmjs.org/jira-mcp-scoped/-/jira-mcp-scoped-1.0.1.tgz","fileCount":8,"unpackedSize":37212,"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/jira-mcp-scoped@1.0.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIE8fZfje+hSRQmcz/dhOf+hGgNy7yrvoUmBG9IY4SXzaAiEA8ANBLysq8ANb2YJZy77ez7MFND7HyCPoqD0biQUzGE8="}]},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:e3ab0e45-b7d8-4970-ba8f-892be89b9a38"}},"directories":{},"maintainers":[{"name":"michalosadowski","email":"osadowskimichal@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/jira-mcp-scoped_1.0.1_1786449175589_0.02810838004213112"},"_hasShrinkwrap":false}},"time":{"created":"2026-08-11T11:44:18.033Z","modified":"2026-08-11T11:52:56.052Z","1.0.0":"2026-08-11T11:44:18.313Z","1.0.1":"2026-08-11T11:52:55.740Z"},"bugs":{"url":"https://github.com/MichalOsadowski/jira-mcp/issues"},"author":{"name":"Michał Osadowski"},"license":"ISC","homepage":"https://github.com/MichalOsadowski/jira-mcp#readme","keywords":["mcp","modelcontextprotocol","jira","atlassian","issue-tracking"],"repository":{"type":"git","url":"git+https://github.com/MichalOsadowski/jira-mcp.git"},"description":"Project-scoped MCP server for Jira — issues, comments, sprints, transitions and attachments over the Jira REST API, narrowed to a single project instead of everything the account can access","maintainers":[{"name":"michalosadowski","email":"osadowskimichal@gmail.com"}],"readme":"# Jira MCP Server\n\nAn MCP (Model Context Protocol) server that lets AI assistants interact with Jira — scoped to a single project (`JIRA_PROJECT_KEY`) instead of everything your account can access.\n\nPublished on npm as [`jira-mcp-scoped`](https://www.npmjs.com/package/jira-mcp-scoped) — run it with `npx -y jira-mcp-scoped`, no clone or install required.\n\nThe server ships in two transports:\n\n- **stdio** (`mcpOverStdio.js`) — the default for local clients (Claude Desktop, Claude Code, Copilot in VS Code). The client spawns the Node process directly.\n- **HTTP** (`mcpOverHttp.js`) — exposes the same tools over a Streamable HTTP endpoint at `/mcp` (default port `3456`). Useful if you want to start the MCP as a stand alone service (e.g in docker) and provide credentials on startup, making them invisible to the AI agent\n\nBoth transports share the same tool implementations in `toolDefinitions.js` and `jiraRestService.js`.\n\n## Logging\n\nThe server logs to **stderr** (so it never corrupts the stdio protocol on stdout). The verbosity is controlled by the `JIRA_LOG_LEVEL` env var:\n\n| Level   | What it logs                                                                                          |\n| ------- | ----------------------------------------------------------------------------------------------------- |\n| `error` | Failures only — failed tool calls and request errors.                                                 |\n| `info`  | _(default)_ Startup config and one line per tool call (name + arguments). Plus everything `error` logs. |\n| `debug` | Per-request Jira API traffic (`→`/`←` with method, path, status), tool result previews, and HTTP session lifecycle. Plus everything `info` logs. |\n\nLong string arguments (e.g. `description`, `comment`) are collapsed to a `<string: N chars>` placeholder so the logs stay readable. The Jira API token is never logged. Each line is formatted as `<ISO timestamp> [jira-mcp] <LEVEL> <message>`.\n\n## Prerequisites\n\n- Node.js 20+\n- A Jira account with API access\n\n## Installation\n\nNo installation needed — MCP clients can run the published package directly via `npx` (see the setup sections below).\n\nFor local development:\n\n```bash\ngit clone https://github.com/MichalOsadowski/jira-mcp.git\ncd jira-mcp\nnpm install\n```\n\n## Testing\n\n```bash\nnpm test\n```\n\nRuns the `node:test` suite (`*.test.js`) with the Jira HTTP layer stubbed — no network access or credentials required.\n\n## Environment variables\n\n| Variable               | Required | Description                                                                                                                                         |\n| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `JIRA_BASE_URL`        | Yes      | Your Jira instance URL, e.g. `https://yourcompany.atlassian.net`                                                                                    |\n| `JIRA_USER_EMAIL`      | Yes      | The email address of your Jira account                                                                                                              |\n| `JIRA_API_TOKEN`       | Yes      | Jira API token — generate one at [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens) |\n| `JIRA_PROJECT_KEY`     | Yes      | The project key, e.g. `PROJ`                                                                                                                      |\n| `JIRA_BOARD_ID`        | No       | Board ID used when placing issues in the current sprint                                                                                             |\n| `JIRA_ATTACHMENTS_DIR` | No       | Directory to save downloaded attachments (default: `./jira-attachments`)                                                                            |\n| `JIRA_LOG_LEVEL`       | No       | Log verbosity: `error`, `info` (default), or `debug`. See [Logging](#logging).                                                                      |\n\n## Setup for Claude Code\n\nAdd the server to your Claude Code MCP configuration.\nFor a repository specific setup add `.mcp.json` in the root of your repository.\n\n```json\n{\n  \"mcpServers\": {\n    \"jira\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"jira-mcp-scoped\"],\n      \"env\": {\n        \"JIRA_BASE_URL\": \"https://yourcompany.atlassian.net\",\n        \"JIRA_USER_EMAIL\": \"you@yourcompany.com\",\n        \"JIRA_API_TOKEN\": \"your-api-token\",\n        \"JIRA_PROJECT_KEY\": \"PROJ\",\n        \"JIRA_BOARD_ID\": \"1\"\n      }\n    }\n  }\n}\n```\n\nRestart Claude Code after saving. You can verify the server is connected by running `/mcp` in the Claude Code CLI.\n\n---\n\n## Setup for GitHub Copilot (VS Code)\n\nAdd the server to `.vscode/mcp.json` in the repository root (create it if it doesn't exist):\n\n```json\n{\n  \"servers\": {\n    \"jira\": {\n      \"type\": \"stdio\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"jira-mcp-scoped\"],\n      \"env\": {\n        \"JIRA_BASE_URL\": \"https://yourcompany.atlassian.net\",\n        \"JIRA_USER_EMAIL\": \"you@yourcompany.com\",\n        \"JIRA_API_TOKEN\": \"your-api-token\",\n        \"JIRA_PROJECT_KEY\": \"PROJ\",\n        \"JIRA_BOARD_ID\": \"1\"\n      }\n    }\n  }\n}\n```\n\n> **Note:** Do not commit `.vscode/mcp.json` if it contains your API token. Add it to `.gitignore` or use VS Code's user-level settings instead (`~/.config/Code/User/settings.json`) under `github.copilot.mcp.servers`.\n\nReload the VS Code window after saving. The Jira tools will appear in the Copilot agent tool list.\n\n---\n\n## Running the HTTP transport\n\nThe HTTP variant is useful when the MCP client cannot spawn a local Node process — e.g. when running Claude inside a container, or pointing a remote agent at a long-lived server.\n\nRun it directly from the cloned repository:\n\n```bash\nJIRA_BASE_URL=... JIRA_USER_EMAIL=... JIRA_API_TOKEN=... JIRA_PROJECT_KEY=PROJ JIRA_BOARD_ID=1 \\\n  npm run start:http\n```\n\nThe server listens on `http://localhost:3456/mcp` (override with `PORT`) and exposes a `/health` endpoint. Environment variables are the same as the stdio transport.\n\nPoint an HTTP-capable MCP client at it:\n\n```json\n{\n  \"mcpServers\": {\n    \"jira\": {\n      \"type\": \"http\",\n      \"url\": \"http://localhost:3456/mcp\"\n    }\n  }\n}\n```\n","readmeFilename":"README.md","contributors":[{"name":"Henrik Holstad","url":"https://github.com/HenrikHolstad"}]}