Download the PHP package stubbedev/atlassian-mcp without Composer

On this page you can find all versions of the php package stubbedev/atlassian-mcp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package atlassian-mcp

atlassian-mcp

A Model Context Protocol (MCP) server for self-hosted Jira (Server / Data Center) and self-hosted Bitbucket (Server / Data Center). Exposes tools for natural-language workflows around tickets, pull requests, review threads, and git context.

Note: This server only supports self-hosted instances. Jira Cloud and Bitbucket Cloud use different APIs and are not supported.


Tools

Workflow

Tool Description
get_dev_context Master entry point: git state + linked Jira ticket + open PR with reviewer/blocker status and next-step hints
start_work Start a Jira ticket: resolves it by key or free-text query (with a picker when several match), creates a local branch (feature/FOO-123-slug) off the repository default branch, fetches the project README from Bitbucket so commit/PR conventions are in context, and optionally transitions the ticket
complete_work Close out finished work: merges the open PR and transitions the Jira ticket to Done. Refuses to merge while reviewers have not approved or a build failed (force=true overrides)

Git

Tool Description
git_get_context Branch, upstream state, remote URL, recent commits, working tree status, diff stat, and Jira keys in branch name. Pass fromRef/toRef for a diff between refs instead, paged via charOffset

Jira

Tool Description
jira_search Discover resources: issues, projects, issue_types, boards, sprints, board_overview, versions, components, fields, or users via resource param
jira_get Full details for one issue: summary, description, status, sprint, transitions, comments, and attachment list
jira_mutate Create, update, transition, comment (commentAction: add / update / delete), upload attachments from a local path, URL, or data: URI, link, add to sprint, log work, change issue type, set any custom field by name (create.customFields / update.customFields), delete an issue (delete=true), or manage a fix version (version.action: create / update / release / archive / delete) — several in one call. Markdown in any text field is converted to Jira wiki markup

Bitbucket

Tool Description
bitbucket_search Discover resources: pull_requests (default), repos, branches, or users via resource param; mine=true for your inbox, narrowed with role=author / reviewer / participant
bitbucket_get_pr Full PR details: metadata, commits, comments, blockers, build status, optional diff, and any attachments referenced from the description or comments
bitbucket_mutate Create/update a PR, or perform lifecycle actions: approve, unapprove, needs_work, merge, decline. Reviewer names are verified against Bitbucket, and an update that would drop existing reviewers needs update.replaceReviewers=true. create.attachments / update.attachments upload files (local path, URL, or data: URI) to the repo and reference them from the description
bitbucket_comment Add, update, or delete a PR comment; for code changes use suggestion so Bitbucket shows Apply suggestion. Enforced here: one reply per thread, no new top-level comment on your own PR (asAuthor=true to override), #123 references rewritten as links. pending=true posts an unpublished draft-review comment. attachments uploads files (local path, URL, or data: URI) and references them from the comment
bitbucket_get_file Raw file content at a branch, tag, or commit — or pass prId to read the PR source branch. Every response names the path and ref it came from, and pages via maxChars/charOffset
bitbucket_pr_tasks Manage PR tasks (checklist items): list, create, resolve, reopen, delete

Shared

Tool Description
get_attachment Fetch an attachment by ID from Jira (source=jira, IDs from jira_get) or Bitbucket (source=bitbucket, IDs from bitbucket_get_pr). Images, videos, animated images (GIF/APNG/animated WebP), audio, and PDFs are decoded inline so the model can see/hear them; text/JSON inline. Oversized or non-renderable attachments are auto-saved to a temp file and the path is returned. saveTo=/absolute/path streams the original to disk
attach_files Open an upload panel in the chat so the user can pick, drag or paste files onto a Jira issue or Bitbucket PR. The panel runs in the host (MCP Apps) and uploads directly, so it works where this server cannot read the filesystem — notably sandboxed Claude Desktop extensions. Degrades to a text answer on hosts without MCP Apps

Resources

URI Description
dev-context://current The same live report as get_dev_context — branch state, linked Jira tickets, open PR — as an MCP resource. Re-read it for fresh state instead of spending another tool call. The repo is resolved per read from the caller's session, so the static URI serves whatever workspace the client is in

Natural language examples


What the server enforces

These are guarantees in the code, not advice in a tool description — a client cannot get them wrong, and they need no prompting:

Setup

1. Create a config file

Create ~/.atlassian-mcp.json:

The $schema field is optional but enables editor autocomplete and validation.

Alternatively, use environment variables (or a .env file in this directory):

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. Install

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, 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 — (see Claude Desktop)
Prebuilt binary download atlassian-mcp_<os>_<arch> from the latest release 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 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 13 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:

Composer asks once whether to trust the plugin. For non-interactive installs (CI, provisioning), allow it up front:

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

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.

Binary cache

npm and Composer download each release's binary once per user, verify it against the release's checksums.txt, and keep it in $XDG_CACHE_HOME/atlassian-mcp/<version>/ (by default ~/.cache on Linux and FreeBSD, ~/Library/Caches on macOS, %LOCALAPPDATA% on Windows), and hardlink it into every install, or copy it where the install is on another filesystem. Further projects and git worktrees on the same version install without downloading anything. Delete old version directories to reclaim their space; installs keep their own link.

Standalone binary (Go, Nix, release download)

Or download atlassian-mcp_<os>_<arch> from the latest release, 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.

CLI-driven clients need one line:

Desktop apps: Claude Desktop installs a one-click .mcpb bundle — 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 when you want to refresh.


Claude Code


Claude Desktop

One-click (recommended). Grab the .mcpb bundle for your platform from the latest release — atlassian-mcp_darwin_arm64.mcpb (Apple Silicon), atlassian-mcp_windows_amd64.mcpb — then double-click it, drag it onto the Claude Desktop window, or use Settings → Extensions → Advanced settings → Install Extension…. The install dialog asks for Jira/Bitbucket URL and token (tokens are stored by Claude Desktop, not in a file) plus Repository, the working tree the git and PR tools default to. Leaving URL/token blank reuses an existing ~/.atlassian-mcp.json.

The bundle carries the binary, so there is no Node, no npx, no PATH to fix and no JSON to edit. MCP Bundles are a Claude Desktop feature today; other clients use the config files below.

Manual config. Claude Desktop is a GUI app: it launches the server with a minimal PATH, no shell, and / as the working directory. So command must be an absolute path (a bare npx fails with spawn npx ENOENT), a .env file or relative --config path never resolves, and nothing expands ~ for you — the server expands a leading ~ in --config / ATLASSIAN_MCP_CONFIG itself, but a client that inserts ~ anywhere else will not. Config file:

To keep npx, set command to the absolute path of your launcher (which npx, e.g. /opt/homebrew/bin/npx) with "args": ["-y", "@stubbedev/atlassian-mcp@latest"].

ATLASSIAN_MCP_REPO_ROOT is what makes get_dev_context, git_get_context, start_work, complete_work and Bitbucket repo auto-detection usable here: a desktop app has no workspace, so it advertises no MCP roots and there is no useful cwd to fall back to. Comma-separate several worktrees (first git repo wins); a per-call repoPath still overrides it.

Server stderr is logged to ~/Library/Logs/Claude/mcp-server-atlassian.log (macOS) or %APPDATA%\Claude\logs\mcp-server-atlassian.log (Windows) — read that first when a connection fails.


Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-only):


Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:


Zed

Add to ~/.config/zed/settings.json:


OpenCode

Add to opencode.json in your project root (or ~/.config/opencode/opencode.json for global):

environment also accepts the JIRA_* / BITBUCKET_* variables if you would rather not keep a config file. Set "type": "remote" with "url" and "headers" to point at a shared HTTP server instead.


Codex (CLI, IDE extension, app)

One command — it writes the config for all three:

Or edit ~/.codex/config.toml directly (.codex/config.toml in a trusted project for a project-scoped server). Note the TOML table name is mcp_servers, with an underscore:

Codex picks the transport from the keys present: command means stdio, url means streamable HTTP. To share one HTTP server:


VS Code / GitHub Copilot

Or commit .vscode/mcp.json with a servers object of the same shape to share it with the repo.


Any other MCP-compatible tool

Most clients accept the Claude Desktop shape — an mcpServers object keyed by name, with command, args and env:

LM Studio uses exactly that shape in its own mcp.json (edit it from the app's plugin panel); Cherry Studio, Witsy, Jan and 5ire have in-app MCP dialogs with the same fields.

Goose is the exception — its ~/.config/goose/config.yaml uses extensions: with cmd rather than command:

Every GUI client brings the caveats from the Claude Desktop section: absolute command path, no usable cwd, no MCP roots — so set ATLASSIAN_MCP_REPO_ROOT.


ChatGPT (desktop / web) — not supported

ChatGPT connectors accept remote HTTPS MCP servers only (streamable HTTP or SSE, with OAuth or no auth); it cannot spawn a local stdio server. This server's --http mode speaks the right protocol, but making it work would mean exposing an endpoint that reaches your 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.


Running as an HTTP server (shared / behind a proxy)

By default the server speaks MCP over stdio (one process per client, launched by your editor). It can instead run as a long-lived Streamable HTTP server that many clients share — useful behind a reverse proxy:

Repo context comes from the client, not the server's working directory. Tools that need a repo (git_get_context, get_dev_context, start_work, complete_work, and Bitbucket project/repo auto-detection) resolve it in this order: an explicit repoPath argument → a root pinned via request header (see below) → ATLASSIAN_MCP_REPO_ROOT (comma-separated for several worktrees — the only workspace signal a GUI desktop client can give) → the client's MCP workspace roots (the server asks via roots/list, caches per session, and refreshes on notifications/roots/list_changed) → the process cwd (stdio only). So one shared HTTP server handles many worktrees: each client's own workspace drives its calls. When a session exposes several roots (multiple worktrees), a tool with no repoPath uses the first git-repo root; pass repoPath (an absolute path, or a worktree name/basename that matches one of the roots) to target a specific worktree. For Bitbucket, passing projectKey+repoSlug explicitly skips repo detection entirely. The repos must be reachable on the server's host (the git tools run git locally).

Pinning the root via a request header (HTTP). A reverse proxy or harness that already knows the working tree can hand it to the server directly, skipping the roots/list round-trip (and working even when the client never advertised the roots capability). Send a file:// URI or absolute path (comma-separated for multiple; first git repo wins):

Accepted header names, in precedence order: X-Repo-Root, X-Mcp-Roots, X-Mcp-Root, Mcp-Roots, Mcp-Root. A header value is authoritative — it takes precedence over roots/list and survives list_changed.

Protocol note: MCP revision 2026-07-28 (SEP-2322/2575) forbids server-initiated JSON-RPC requests, so roots/list is unavailable on that revision — the server says so explicitly instead of hanging. On 2026-07-28 clients, a root header (or an explicit repoPath / projectKey+repoSlug) is the only way to give the server repo context.

Client config for an already-running HTTP server (Claude Code example):

Attachment upload sources

Every attachments argument — jira_mutate, bitbucket_mutate (create/update) and bitbucket_comment — takes sources, not only paths. Each entry is one of:

Source Example Notes
Local file path /tmp/shot.png, file:///tmp/shot.png Requires the server to share a filesystem with the file
http(s) URL https://example.com/diagram.png Downloaded by the server. Filename comes from Content-Disposition, else the URL's last path segment, with an extension filled in from Content-Type
data: URI data:text/plain;name=run.log;base64,Ym9vbQ== Bytes inlined in the argument. ;name= titles the file; without it the name is derived from the media type

A URL whose host matches the configured Jira or Bitbucket instance is fetched with your token, so an attachment that already lives on one service can be re-attached to the other by URL. Tokens are never sent to any other host. Downloads are capped at 250 MB.

For Bitbucket, a source that already appears in the description or comment text is replaced in place by the attachment markup — that works for URLs too, so writing ![the widget](https://…/shot.png) and passing the same URL in attachments keeps your caption and swaps in the uploaded file.

Confined hosts. A host may run this server sandboxed, in which case a path it was not granted comes back as a permission error while URL and data: sources keep working — neither needs the filesystem. The startup log names the config file it read, or the error it got trying, which is the quickest way to tell whether the filesystem is restricted on your setup. The same applies to chaining with another MCP server: a screenshot another server wrote to its temp directory is only reachable here if this process is allowed to read that path.

Files a user attaches to the chat itself cannot be uploaded from these arguments: MCP has no mechanism for passing conversation attachments to a server, and the model cannot re-emit image bytes it was shown. Use attach_files — the user re-picks or pastes the file into a panel that uploads it directly — or give this server a URL or a readable path.

The upload panel (MCP Apps)

attach_files opens a file picker inside the chat. It exists for the file that has no path to pass:

Where a readable path or a URL does exist, the attachments arguments remain the better route — no user interaction at all.

MCP Apps routes around both. The tool declares a ui:// resource, the host renders it as an iframe, and that iframe is an ordinary browser: its file picker, drop target and paste handler sit outside the server's sandbox. It hands the bytes back as data: URIs through tools/call, which is the same source format the attachments arguments take.

The model passes only the target (issueKey, or prId with an optional commentId); it never fills in files and never sees the file contents. Files are capped at 12 MB each, since the bytes ride the JSON-RPC channel as base64 — anything larger should go up by URL.

Support is negotiated: hosts advertise MCP Apps through the io.modelcontextprotocol/ui extension at initialize. Where it is absent — Claude Code today — the whole surface is hidden rather than merely degraded: attach_files is filtered out of tools/list, the widget is filtered out of resources/list, and reading it is refused (a client that fetched it anyway would take a few hundred KB of inlined SDK into its context for a page it cannot draw). Such a host sees exactly the tools it saw before, and is told to ask for a path or URL instead.

The panel is one self-contained HTML document (ui/upload.html, ~19 KB), because the host serves it under default-src 'none': no CDN, no second resource, no build step. It carries its own ~2 KB MCP Apps bridge rather than the official browser SDK — a view only needs one ui/initialize round trip, an initialized notification, tool-input notifications in and tools/call requests out, and the SDK brings ~400 KB of zod to validate messages this page already treats as untrusted. Bundling it with esbuild makes it larger, not smaller.

Attachment decoding pipeline

The get_attachment tool decodes binary attachments into model-readable content before returning them:

Input What gets returned How
Static images (PNG/JPEG/WebP/BMP/TIFF/GIF/SVG/AVIF/HEIC/JPEG XL…) Resized image content blocks imaging, long edge ≤ maxDimension, default 1568; EXIF auto-orient; PNG for alpha, else JPEG. AVIF/HEIC/JPEG XL via gen2brain decoders (libavif/libheif/libjxl compiled to WebAssembly)
Animated images (GIF/APNG/animated WebP) N sampled frames as image content blocks composited in Go, as a browser shows them (default 6 frames @ 768 px)
Video (MP4/MOV, MKV/WebM, AVI) N sampled frames as image content blocks H.264 via goh264 (GOPs decoded in parallel), Motion JPEG, and VP8 keyframes only (x/image/vp8 has no inter frames); MP4 demuxed by mp4ff, Matroska and AVI in-tree. Uniform or scene-change sampling (ffmpeg's scene metric), near-duplicate frames dropped. Re-call with start, end, frames, mode, sceneThreshold to zoom in. HEVC, VP9, AV1 and MPEG-4 Part 2 are reported as unsupported; pass saveTo to keep the original
Audio (mp3/wav/ogg/…) MCP audio content block passthrough
PDFs Extracted text — or rasterized pages if text is empty (scanned PDFs) text via ledongthuc/pdf; pages rendered by PDFium compiled to WebAssembly (go-pdfium)
Text-like (json/xml/yaml/…) Text content block passthrough
Everything else (or oversized) Auto-saved to a temp file; path is returned os.TempDir() with atlmcp- prefix

Auto-saved files are periodically pruned by TTL and total-size quota — see Environment overrides below.

No external tools

The binary is self-contained and built without cgo (release builds use -tags nodynamic, so the image decoders never look for system libraries). Git access goes through go-git (status, log, diff, branch, checkout, fetch, push); the C libraries some formats need (PDFium, libavif, libheif, libjxl) run as embedded WebAssembly under wazero.

Git credentials for fetch/push come from where git keeps them, minus anything that needs another program: ssh-agent, IdentityFile entries in ~/.ssh/config and unencrypted ~/.ssh/id_* keys (host keys checked against ~/.ssh/known_hosts); for https, credentials in the URL, ~/.git-credentials, ~/.netrc, and the Bitbucket token itself for the configured Bitbucket host. Credential helpers, passphrase prompts, git hooks and Git LFS smudging do not run.

goh264 is LGPL-2.1; it is linked unmodified and the full source of this server is public, so the binary can be rebuilt against a modified copy.

Environment overrides

Variable Purpose Default
ATLASSIAN_MCP_HTTP Run as a Streamable HTTP server instead of stdio. 1/true → 127.0.0.1:7337; or set an explicit host:port. Same as --http. unset (stdio)
ATLASSIAN_MCP_HTTP_TOKEN Bearer token for HTTP mode. Optional on loopback binds; required on non-loopback binds. unset
ATLASSIAN_MCP_REPO_ROOT Default workspace root(s) for the git/PR tools, comma-separated. file:// URIs, absolute paths, ~/… and Windows drive paths all work. Needed by clients that expose no MCP roots (desktop apps). Overridden by a repoPath argument or a root header. unset
ATLASSIAN_MCP_MARK_AI_TEXT Set false to stop appending the bold [AI] attribution line to Jira/Bitbucket text this server posts. true
ATLASSIAN_MCP_TMP_TTL_DAYS Auto-saved attachments older than this are pruned. 7
ATLASSIAN_MCP_TMP_MAX_BYTES Total-size quota for auto-saved attachments in os.tmpdir(). When exceeded, oldest are evicted. 1073741824 (1 GB)

Releases (Maintainers)

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).

On a pushed v* tag, .github/workflows/publish.yml cross-compiles the Go binary for 13 OS/arch targets, packs five of them into .mcpb bundles for one-click desktop install (packaging/mcpb/pack.sh, macOS arm64 and Windows/Linux × amd64/arm64), attaches everything to a GitHub release, and publishes the npm wrapper (which downloads the matching binary on install). just bundle builds a bundle for the host platform locally.

Release flow (just drives it; it refuses to run on a dirty tree):

just release-<level> bumps the version in package.json, re-syncs the Nix vendorHash (just sync-flake), runs the gates (just check), commits release: vX.Y.Z, tags, and pushes both the branch and the tag. The tag push triggers publish.yml.

package.json is the single source of truth for the version: the binary embeds it via go:embed (no -ldflags) and nix/package.nix reads it, so one bump moves everything. The equivalent npm scripts (npm run release:patch / :minor / :major) still work.

Required npm setup (one-time):

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

Jira Server / Data Center

Personal Access Tokens are supported from Jira 8.14 onwards.

  1. Log in to your Jira instance.
  2. Click your profile avatar in the top-right corner and select Profile.
  3. In the left sidebar, click Personal Access Tokens.
  4. Click Create token.
  5. Give the token a name (e.g. atlassian-mcp) and optionally set an expiry date.
  6. Click Create and copy the token — it will only be shown once.

Paste the token as the token value under jira in your config file.

If your Jira version is older than 8.14, you can use HTTP Basic Auth instead — but this server only supports Bearer token (PAT) authentication.

Bitbucket Server / Data Center

Personal Access Tokens are supported from Bitbucket Server 5.5 onwards.

  1. Log in to your Bitbucket instance.
  2. Click your profile avatar in the top-right corner and select Manage account.
  3. In the left sidebar, under Security, click Personal access tokens.
  4. Click Create a token.
  5. Give the token a name (e.g. atlassian-mcp).
  6. Set the permissions:
    • Projects: Read
    • Repositories: Read + Write (Write is needed to create pull requests and add comments)
  7. Optionally set an expiry date.
  8. Click Create and copy the token — it will only be shown once.

Paste the token as the token value under bitbucket in your config file.


Development

The server is a single Go module at the repo root (no src/ tree).

Tasks live in the justfile and mirror the CI gates, so a green just check predicts green CI:

Tool schemas live in tools.json (embedded into the binary) and the MCP protocol layer is the official modelcontextprotocol/go-sdk; the Go files at the repo root hold the tool logic.


All versions of atlassian-mcp with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer-plugin-api Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package stubbedev/atlassian-mcp contains the following files

Loading the files please wait ...