@stubbedev/atlassian-mcp 0.5.23 → 0.5.24

package/README.md

@@ -171,9 +171,95 @@ BITBUCKET_ACCESS_TOKEN=your-bitbucket-personal-access-token
 
 Config is resolved in this order: `--config <path>` CLI arg → `ATLASSIAN_MCP_CONFIG` env var → `~/.atlassian-mcp.json` → `$XDG_CONFIG_HOME/atlassian-mcp/config.json` (default `~/.config/atlassian-mcp/config.json`) → `.atlassian-mcp.json` in cwd → environment variables. A leading `~` in the first two is expanded by the server, so a client that spawns it without a shell still resolves the path. Within a file, per-field: a value in the config file wins, environment variables fill the gaps.
 
-### 2. Connect to your AI tool
+### 2. Install
 
-No cloning or building required — just point your tool at `npx @stubbedev/atlassian-mcp@latest` and it will install and run automatically.
+Every option below runs the same single static Go binary — no `git`, `ffmpeg` or other
+program needed on the machine. Pick whichever package manager you already have:
+
+| Option | Install | Command for your MCP client |
+|---|---|---|
+| **npx** (Node 18+) | nothing — fetched on first run | `npx -y @stubbedev/atlassian-mcp@latest` |
+| **npm global** (Node 18+) | `npm install -g @stubbedev/atlassian-mcp` | `atlassian-mcp` |
+| **Composer** (PHP 8.1+) | `composer global require stubbedev/atlassian-mcp` | the native binary it downloads — see [Composer](#composer) |
+| **Composer, per project** | `composer require --dev stubbedev/atlassian-mcp` | `vendor/stubbedev/atlassian-mcp/bin/atlassian-mcp-native` |
+| **Claude Desktop bundle** | double-click the `.mcpb` from the [latest release](https://github.com/stubbedev/atlassian-mcp/releases/latest) | — (see [Claude Desktop](#claude-desktop)) |
+| **Prebuilt binary** | download `atlassian-mcp_<os>_<arch>` from the [latest release](https://github.com/stubbedev/atlassian-mcp/releases/latest) | path to that file |
+| **Go** | `go install -tags nodynamic github.com/stubbedev/atlassian-mcp@latest` | `atlassian-mcp` (in `$GOBIN`) |
+| **Nix** | `nix profile install github:stubbedev/atlassian-mcp` | `atlassian-mcp` |
+
+The client examples in [step 3](#3-connect-to-your-ai-tool) use `npx`. With any other
+option, replace `npx -y @stubbedev/atlassian-mcp@latest` (or `"command": "npx"` plus its
+`args`) with that option's command. MCP clients often start servers without your shell's
+`PATH`, so an absolute path is the safest choice (`which atlassian-mcp`).
+
+#### npm / npx
+
+`npx` downloads the package and the prebuilt binary for your platform on first run, so
+there is nothing to install up front. `npm install -g` does the same once and puts
+`atlassian-mcp` on your `PATH`.
+
+#### Composer
+
+The Composer package `stubbedev/atlassian-mcp` is for PHP projects, or machines with PHP
+but no Node. It is a Composer plugin: on `composer install` / `update` it downloads the
+prebuilt binary for your OS and architecture (the same 14 targets as npm), from the release
+matching the installed version, so a pinned version pins the binary. Your MCP client then
+runs that native binary directly, and PHP is never in the request path:
+
+```bash
+composer require --dev stubbedev/atlassian-mcp      # per project
+composer global require stubbedev/atlassian-mcp     # per user
+```
+
+Composer asks once whether to trust the plugin. For non-interactive installs (CI,
+provisioning), allow it up front:
+
+```bash
+composer config allow-plugins.stubbedev/atlassian-mcp true          # per project
+composer global config allow-plugins.stubbedev/atlassian-mcp true   # per user
+```
+
+The install prints the binary's path. Point your client at it:
+
+| Install | Native binary (no PHP at runtime) | PHP launcher |
+|---|---|---|
+| per project | `vendor/stubbedev/atlassian-mcp/bin/atlassian-mcp-native` | `vendor/bin/atlassian-mcp` |
+| per user | `$(composer global config home)/vendor/stubbedev/atlassian-mcp/bin/atlassian-mcp-native` | `$(composer global config bin-dir --absolute)/atlassian-mcp` |
+
+```bash
+claude mcp add atlassian -- "$PWD/vendor/stubbedev/atlassian-mcp/bin/atlassian-mcp-native" --config ~/.atlassian-mcp.json
+```
+
+On Windows the binary is `atlassian-mcp-native.exe`. The PHP launcher works even if
+you declined the plugin: it downloads the binary on its first run, then hands over to it.
+Clients start the server from their own working directory, so use absolute paths. Set
+`ATLASSIAN_MCP_SKIP_DOWNLOAD=1` to skip the install-time download.
+
+#### Standalone binary (Go, Nix, release download)
+
+```bash
+go install -tags nodynamic github.com/stubbedev/atlassian-mcp@latest   # → $GOBIN / $GOPATH/bin
+nix run github:stubbedev/atlassian-mcp -- --config ~/.atlassian-mcp.json
+```
+
+Or download `atlassian-mcp_<os>_<arch>` from the
+[latest release](https://github.com/stubbedev/atlassian-mcp/releases/latest), then
+`chmod +x` it (macOS/Linux/FreeBSD).
+
+#### Updating
+
+| Option | Update |
+|---|---|
+| npx | `npx clear-npx-cache`, then restart your MCP client |
+| npm global | `npm update -g @stubbedev/atlassian-mcp` |
+| Composer | `composer global update stubbedev/atlassian-mcp` (or `composer update stubbedev/atlassian-mcp` in the project) |
+| Claude Desktop | install the newer `.mcpb` over the old one |
+| Go / Nix / binary | re-run the install command or download the newer release |
+
+### 3. Connect to your AI tool
+
+The examples below use `npx`. If you installed another way, swap in that option's command
+from the [table above](#2-install).
 
 CLI-driven clients need one line:
 
@@ -181,12 +267,14 @@ CLI-driven clients need one line:
 claude mcp add atlassian -- npx -y @stubbedev/atlassian-mcp@latest       # Claude Code
 codex mcp add atlassian -- npx -y @stubbedev/atlassian-mcp@latest        # Codex CLI / IDE / app
 code --add-mcp '{"name":"atlassian","command":"npx","args":["-y","@stubbedev/atlassian-mcp@latest"]}'   # VS Code
+
+claude mcp add atlassian -- atlassian-mcp                                 # e.g. after npm -g / Composer / Go / Nix
 ```
 
 Desktop apps: **Claude Desktop** installs a one-click [`.mcpb` bundle](#claude-desktop) —
 no Node, no JSON. Everything else takes a config file; see below.
 
-> Note: `--prefer-online` can break MCP startup in some clients. Keep the command simple and use the update steps below when you want to refresh.
+> Note: `--prefer-online` can break MCP startup in some clients. Keep the command simple and use the [update steps](#updating) when you want to refresh.
 
 ---
 
@@ -429,37 +517,8 @@ the right protocol, but making it work would mean exposing an endpoint that reac
 self-hosted Jira/Bitbucket to OpenAI's servers, and ChatGPT offers no place for the static
 bearer token this server uses. Use a client from the list above.
 
-### Updating existing installs
-
-If your MCP client is already configured and you want the newest package version:
-
-```bash
-npx clear-npx-cache
-```
-
-Then restart your MCP client.
-
 ---
 
-### Install without npm
-
-The server is a single static Go binary. The `npx` path above downloads the prebuilt
-binary for your platform on first run; these alternatives skip Node entirely — as does the
-[`.mcpb` bundle](#claude-desktop) for Claude Desktop, and the per-platform binaries
-attached to every [release](https://github.com/stubbedev/atlassian-mcp/releases/latest):
-
-```bash
-# Go toolchain — installs to $GOBIN / $GOPATH/bin
-go install -tags nodynamic github.com/stubbedev/atlassian-mcp@latest
-
-# Nix flake
-nix run github:stubbedev/atlassian-mcp -- --config ~/.atlassian-mcp.json
-```
-
-Then point your MCP client's `command` at the resulting `atlassian-mcp` binary
-instead of `npx`. Every install path is the same single static binary: it needs no `git`,
-`ffmpeg` or other program on the machine.
-
 ### Running as an HTTP server (shared / behind a proxy)
 
 By default the server speaks MCP over **stdio** (one process per client, launched
@@ -650,7 +709,8 @@ the binary can be rebuilt against a modified copy.
 
 ## Releases (Maintainers)
 
-This package is published to npm as `@stubbedev/atlassian-mcp`.
+This package is published to npm as `@stubbedev/atlassian-mcp` and to Packagist as
+`stubbedev/atlassian-mcp`.
 
 Use semantic versioning for releases. Breaking tool-surface changes should bump the minor version while `<1.0.0` (for example `0.0.x` -> `0.1.0`).
 
@@ -681,6 +741,12 @@ Required npm setup (one-time):
 
 - In npm package settings, add this GitHub repo/workflow as a Trusted Publisher
 
+Packagist needs no workflow step: it reads `composer.json` straight from each pushed `v*`
+tag (no `version` field — the tag is the version, and the launcher reads `package.json`
+to pick the release binary). One-time setup: submit the repo at
+<https://packagist.org/packages/submit> and keep the Packagist GitHub integration enabled
+so new tags are picked up automatically.
+
 ---
 
 ## Creating Personal Access Tokens

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stubbedev/atlassian-mcp",
-  "version": "0.5.23",
+  "version": "0.5.24",
   "description": "MCP server for self-hosted Jira and Bitbucket (Go, distributed as a prebuilt binary)",
   "license": "MIT",
   "type": "module",