atlassian-agent-mcp 0.3.0__tar.gz

atlassian_agent_mcp-0.3.0/.editorconfig

@@ -0,0 +1,23 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.py]
+indent_style = space
+indent_size = 4
+
+[*.{yml,yaml,json,toml}]
+indent_style = space
+indent_size = 2
+
+[Makefile]
+indent_style = tab
+
+[*.md]
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = false

atlassian_agent_mcp-0.3.0/.env.example

@@ -0,0 +1,11 @@
+# Copy to .env and fill in. .env is gitignored and must never be committed.
+# Both services use a personal access token, sent as:
+#   Authorization: Bearer <token>
+
+# Confluence — required by the confluence_* tools.
+CONFLUENCE_URL=https://confluence.example.com
+CONFLUENCE_TOKEN=your-personal-access-token
+
+# Jira — required only by the jira_* tools. Leave unset to run Confluence-only.
+JIRA_URL=https://jira.example.com
+JIRA_TOKEN=your-personal-access-token

atlassian_agent_mcp-0.3.0/.github/dependabot.yml

@@ -0,0 +1,41 @@
+---
+# Both ecosystems here exist because this repository pins things by hand and a
+# hand-written pin is a pin that rots. The actions in the workflows are pinned
+# to commit SHAs, which is the right thing for supply-chain reasons and also
+# the reason nobody would ever notice a security fix: a SHA never moves.
+version: 2
+
+updates:
+  # The workflows run with this repository's token. An action pinned to a SHA
+  # is safe from a moved tag and blind to a patched vulnerability, so something
+  # has to bring the new SHA to a pull request where it can be read.
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: "ci"
+    groups:
+      actions:
+        patterns: ["*"]
+
+  # uv.lock is committed, so a dependency only ever moves when somebody moves
+  # it. Grouped, because a lockfile refresh that arrives as eight separate pull
+  # requests gets ignored as eight separate pull requests.
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: "chore"
+    groups:
+      dev-dependencies:
+        dependency-type: development
+        patterns: ["*"]
+      runtime-dependencies:
+        dependency-type: production
+        # Kept separate and ungrouped from dev: atlassian-python-api and
+        # fastmcp are capped at a major for reasons written into pyproject.toml,
+        # and a major bump of either needs the comment read, not merged.
+        patterns: ["*"]
+        update-types: ["minor", "patch"]

atlassian_agent_mcp-0.3.0/.github/workflows/ci.yml

@@ -0,0 +1,77 @@
+---
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  # So the release workflow can run exactly this gate rather than a copy of it
+  # that drifts. Nothing reaches PyPI without passing what main passes.
+  workflow_call:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+# Every action is pinned to a commit, not a tag: a tag can be moved onto other
+# code, and an action runs with access to this workflow's token. The comment
+# after each one says which release the commit is, for the human reading it.
+jobs:
+  test:
+    name: test (py${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install the project
+        run: uv sync --frozen
+
+      - name: Lint
+        run: uv run ruff check --output-format=github .
+
+      - name: Format
+        run: uv run ruff format --check .
+
+      - name: Typecheck
+        run: uv run mypy
+
+      # No Atlassian credentials exist in CI, and none should: the suite fakes
+      # the HTTP layer, so a test that needs a live Jira is a test that has
+      # stopped testing this repository.
+      - name: Test
+        run: uv run pytest
+
+      # The MCP surface is the product. Listing it without credentials catches
+      # a tool that fails to register long before an agent session does.
+      - name: MCP tools register
+        run: uv run python scripts/list_mcp_tools.py
+
+  secrets:
+    name: gitleaks
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          # Full history: a token committed once and reverted is still leaked.
+          fetch-depth: 0
+
+      - name: Scan history for secrets
+        uses: gitleaks/gitleaks-action@ff98106e4c7b2bc287b24eaf42907196329070c7 # v2.3.9
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

atlassian_agent_mcp-0.3.0/.github/workflows/release.yml

@@ -0,0 +1,116 @@
+---
+name: Release
+
+# Publishes to PyPI when a `v*` tag is pushed. Tagging is the whole release.
+#
+# There is no token anywhere — not in the repository, not in a secret, not on
+# anyone's laptop. PyPI's trusted publishing exchanges this workflow's OIDC
+# identity for a credential that lasts minutes, which is the same reason this
+# project keeps Atlassian tokens in the environment rather than in a file.
+# Three things are load-bearing rather than decorative, and PyPI matches on all
+# of them: the filename `release.yml`, the `pypi` environment, and
+# `id-token: write`. Rename any of them and the upload fails with a 403 that
+# does not explain itself.
+#
+# The distribution is `atlassian-agent-mcp`, not `atlassian-agent`: that name
+# belongs to an unrelated project on PyPI. The import package is still
+# `atlassian_agent`.
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  # The same gate main gets, called rather than copied. A tag that cannot pass
+  # CI is not a release.
+  ci:
+    uses: ./.github/workflows/ci.yml
+
+  # Build and publish are separate jobs on purpose. Only `publish` can mint a
+  # PyPI credential, and all it does is upload files it did not produce; the
+  # build — which runs hatchling and resolves the dependency tree, i.e. other
+  # people's code — never holds one.
+  build:
+    name: build and check the artifacts
+    needs: ci
+    runs-on: ubuntu-latest
+    steps:
+      # Pinned to a commit, not a tag: a tag can be moved onto other code.
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+          python-version: "3.13"
+
+      # A tag is typed by hand and the version lives in a file, so the two can
+      # disagree. Without this, tagging v0.3.0 on a tree that still says 0.2.0
+      # publishes 0.2.0 under a tag claiming otherwise — and a version on PyPI
+      # cannot be replaced, only yanked.
+      - name: the tag must be the version being published
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          version=$(uv run --no-project python -c \
+            'import tomllib,pathlib; print(tomllib.loads(pathlib.Path("pyproject.toml").read_text())["project"]["version"])')
+          if [ "$tag" != "$version" ]; then
+            echo "::error::tag $GITHUB_REF_NAME does not match pyproject version $version"
+            exit 1
+          fi
+          echo "publishing $version"
+
+      # A release nobody can read the notes for is half a release, and the
+      # changelog is the only place this project records what changed.
+      - name: the changelog must have an entry for this version
+        run: |
+          version="${GITHUB_REF_NAME#v}"
+          grep -q "^## \[$version\]" CHANGELOG.md || {
+            echo "::error::CHANGELOG.md has no '## [$version]' heading"
+            exit 1
+          }
+          echo "changelog entry found"
+
+      - name: build
+        run: uv build
+
+      - name: the artifacts are well-formed
+        run: uvx twine check dist/*
+
+      # Installing the wheel somewhere clean is the last cheap point at which
+      # a packaging mistake is noticeable: every test above imports from the
+      # working tree, where a missing module or an unresolvable entry point is
+      # invisible. The same script backs `make dist-check`, so the rehearsal
+      # somebody runs before tagging is this exact check.
+      - name: the installed wheel runs, and registers every tool
+        run: scripts/verify-wheel.sh dist/*.whl
+
+      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+
+  publish:
+    name: publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/atlassian-agent-mcp
+    permissions:
+      id-token: write # the whole mechanism; without it there is no credential
+    steps:
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: dist
+          path: dist/
+
+      # `always`, not `automatic`: if trusted publishing is unavailable for any
+      # reason, fail rather than quietly looking for a token that should not
+      # exist.
+      - name: publish
+        run: uv publish --trusted-publishing always

atlassian_agent_mcp-0.3.0/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer,
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

atlassian_agent_mcp-0.3.0/.pre-commit-config.yaml

@@ -0,0 +1,76 @@
+---
+# Install with: uv run pre-commit install --install-hooks
+# Run over everything with: uv run pre-commit run --all-files
+default_install_hook_types: [pre-commit, commit-msg]
+default_language_version:
+  python: python3.11
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-added-large-files
+        args: [--maxkb=512]
+        # uv.lock is a generated text file we deliberately commit, and it is
+        # legitimately over the limit. Excluding it by name keeps the guard
+        # tight for everything else rather than raising it globally.
+        exclude: ^uv\.lock$
+      - id: check-merge-conflict
+      - id: check-toml
+      - id: check-yaml
+      - id: detect-private-key
+      - id: end-of-file-fixer
+      - id: mixed-line-ending
+        args: [--fix=lf]
+      - id: trailing-whitespace
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.15
+    hooks:
+      - id: ruff-check
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: https://github.com/astral-sh/uv-pre-commit
+    rev: 0.9.28
+    hooks:
+      # Keeps uv.lock honest whenever pyproject.toml moves.
+      - id: uv-lock
+
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.30.1
+    hooks:
+      - id: gitleaks
+
+  - repo: local
+    hooks:
+      # The upstream mypy mirror runs in its own isolated environment and
+      # cannot see project dependencies, which produces phantom import errors.
+      # Run the project's own mypy instead.
+      - id: mypy
+        name: mypy
+        entry: uv run --frozen mypy
+        language: system
+        types: [python]
+        pass_filenames: false
+        require_serial: true
+
+      # This repository's whole point is that Atlassian credentials stay in the
+      # environment. A committed .env would defeat it, so refuse it explicitly
+      # rather than relying on .gitignore, which a `git add -f` walks straight
+      # past.
+      - id: no-dotenv-committed
+        name: no .env committed
+        language: fail
+        files: '^\.env$|(^|/)\.env\.(local|[^.]*)$'
+        exclude: '(^|/)\.env\.example$'
+        entry: >-
+          .env files hold live Atlassian tokens and must never be committed.
+          Put placeholders in .env.example instead.
+
+      - id: no-agent-coauthors
+        name: no AI Co-Authored-By trailers
+        language: pygrep
+        stages: [commit-msg]
+        args: [--ignore-case, --multiline]
+        entry: 'co-authored-by:.*(claude|anthropic|copilot|cursor|gemini|codex|chatgpt|openai)'

atlassian_agent_mcp-0.3.0/.python-version

@@ -0,0 +1 @@
+3.11