Atlassian Agent

CLI or API | MCP | Agent

Version: 2.0.0

Documentation — Installation, deployment, and usage across the MCP, Python API, and CLI interfaces, along with guidance for connecting to Atlassian Cloud and Server instances, are maintained in the official documentation.

---

Overview

Atlassian Agent is a production-grade Agent and Model Context Protocol (MCP) server designed to interface directly with Comprehensive AI agent for Jira and Confluence management..

---

Key Features

• Consolidated Action-Routed MCP Tools: Minimizes token overhead and eliminates tool bloat in LLM contexts by grouping methods into optimized, togglable tool modules.
• Enterprise-Grade Security: Comprehensive support for Eunomia policies, OIDC token delegation, and granular execution context tracking.
• Integrated Graph Agent: Built-in Pydantic AI agent supporting the Agent Control Protocol (ACP) and standard Web interfaces (AG-UI).
• Native Telemetry & Tracing: Out-of-the-box OpenTelemetry exports and native Langfuse tracing.

---

CLI or API

This agent wraps the Comprehensive AI agent for Jira and Confluence management. API. You can interact with it programmatically or via its integrated execution entrypoints.

Detailed instructions on how to use the underlying API wrappers, extended schema bindings, and developer SDK references are maintained in docs/index.md.

---

MCP

This server utilizes dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.

Available MCP Tools

The table below is auto-generated from the live server — do not edit by hand.

Condensed action-routed tools (default — MCP_TOOL_MODE=condensed)

MCP Tool	Toggle Env Var	Description
atlassian_atlassian	ATLASSIANTOOL	Manage atlassian operations.
atlassian_atlassian_admin	ATLASSIAN_ADMINTOOL	Manage atlassian admin operations.
atlassian_atlassian_api_access	ATLASSIAN_API_ACCESSTOOL	Manage atlassian api access operations.
atlassian_atlassian_control	ATLASSIAN_CONTROLTOOL	Manage atlassian control operations.
atlassian_atlassian_dlp	ATLASSIAN_DLPTOOL	Manage atlassian dlp operations.
atlassian_atlassian_org	ATLASSIAN_ORGTOOL	Manage atlassian org operations.
atlassian_atlassian_user_mgmt	ATLASSIAN_USER_MGMTTOOL	Manage atlassian user mgmt operations.
atlassian_atlassian_user_provisioning	ATLASSIAN_USER_PROVISIONINGTOOL	Manage atlassian user provisioning operations.
atlassian_confluence_other	CONFLUENCE_OTHERTOOL	Manage Confluence other operations.
atlassian_confluence_page	CONFLUENCE_PAGETOOL	Manage Confluence page operations.
atlassian_confluence_space	CONFLUENCE_SPACETOOL	Manage Confluence space operations.
atlassian_confluence_user	CONFLUENCE_USERTOOL	Manage Confluence user operations.
atlassian_jira_comment	JIRA_COMMENTTOOL	Manage Jira comment operations.
atlassian_jira_field	JIRA_FIELDTOOL	Manage Jira field operations.
atlassian_jira_issue	JIRA_ISSUETOOL	Manage Jira issue operations.
atlassian_jira_other	JIRA_OTHERTOOL	Manage Jira other operations.
atlassian_jira_project	JIRA_PROJECTTOOL	Manage Jira project operations.
atlassian_jira_screen	JIRA_SCREENTOOL	Manage Jira screen operations.
atlassian_jira_user	JIRA_USERTOOL	Manage Jira user operations.
atlassian_jira_workflow	JIRA_WORKFLOWTOOL	Manage Jira workflow operations.

Verbose 1:1 API-mapped tools (MCP_TOOL_MODE=verbose or both)

1 per-operation tools — one per public API method (click to expand)

MCP Tool	Toggle Env Var	Description
atlassian_request	BASE_ATLASSIAN_CLIENTTOOL	Invoke the request operation.

20 action-routed tool(s) (default) · 1 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (condensed default · verbose 1:1 · both). Auto-generated — do not edit.

Detailed tool schemas, parameter shapes, and validation constraints are preserved in docs/usage.md.

Dynamic Tool Selection & Visibility

This MCP server supports dynamic toolset selection and visibility filtering at runtime. This allows you to restrict the set of exposed tools in order to prevent blowing up the LLM's context window.

You can configure tool filtering via multiple input channels:

• CLI Arguments: Pass --tools or --toolsets (or their disabled counterparts --disabled-tools and --disabled-toolsets) during startup.
• Environment Variables: Define standard environment variables:
  • MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS
  • MCP_ENABLED_TAGS / MCP_DISABLED_TAGS
• HTTP SSE Request Headers: Pass custom headers during transport initialization:
  • x-mcp-enabled-tools / x-mcp-disabled-tools
  • x-mcp-enabled-tags / x-mcp-disabled-tags
• HTTP SSE Request Query Parameters: Append query parameters directly to your transport connection URL:
  • ?tools=tool1,tool2
  • ?tags=tag1

When query strings or parameters are supplied, an LLM-free Knowledge Graph resolution layer (using DynamicToolOrchestrator) matches query intents against known tool tags, names, or descriptions, with safe fallback and automated 24-hour background cache refreshing.

---

MCP Configuration Examples

Install the connector-focused [mcp] extra. Examples use atlassian-agent[mcp] to add FastMCP / FastAPI through agent-utilities[mcp]; the required Agent Utilities core still carries epistemic-graph[full]. The [agent-runtime] extra additionally enables model orchestration.

stdio Transport (local IDEs — Cursor, Claude Desktop, VS Code)

{
  "mcpServers": {
    "atlassian-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "atlassian-agent[mcp]",
        "atlassian-mcp"
      ],
      "env": {
        "MCP_TOOL_MODE": "intent",
        "ATLASSIANTOOL": "True",
        "ATLASSIAN_ADMINTOOL": "True",
        "ATLASSIAN_AGENT_TOKEN": "your_token_here",
        "ATLASSIAN_AGENT_URL": "http://localhost:8080",
        "ATLASSIAN_AGENT_USER": "[email protected]",
        "ATLASSIAN_API_ACCESSTOOL": "True",
        "ATLASSIAN_BEARER_TOKEN": "your_personal_access_token",
        "ATLASSIAN_CONTROLTOOL": "True",
        "ATLASSIAN_DLPTOOL": "True",
        "ATLASSIAN_OAUTH_TOKEN": "your_3lo_access_token",
        "ATLASSIAN_ORGTOOL": "True",
        "ATLASSIAN_USER_MGMTTOOL": "True",
        "ATLASSIAN_USER_PROVISIONINGTOOL": "True",
        "AUDIENCE": "https://your-instance.atlassian.net",
        "CONFLUENCE_OTHERTOOL": "True",
        "CONFLUENCE_PAGETOOL": "True",
        "CONFLUENCE_SPACETOOL": "True",
        "CONFLUENCE_USERTOOL": "True",
        "DELEGATED_SCOPES": "read:jira-work write:jira-work",
        "JIRA_COMMENTTOOL": "True",
        "JIRA_FIELDTOOL": "True",
        "JIRA_ISSUETOOL": "True",
        "JIRA_OTHERTOOL": "True",
        "JIRA_PROJECTTOOL": "True",
        "JIRA_SCREENTOOL": "True",
        "JIRA_USERTOOL": "True",
        "JIRA_WORKFLOWTOOL": "True",
        "KGTOOL": "True"
      }
    }
  }
}

Runtime references require an alias-aware launcher such as GraphOS. Other launchers must omit those entries and inject the resolved values through their own runtime secret boundary.

Streamable-HTTP Transport (networked / production)

{
  "mcpServers": {
    "atlassian-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "atlassian-agent[mcp]",
        "atlassian-mcp",
        "--transport",
        "streamable-http",
        "--port",
        "8000"
      ],
      "env": {
        "TRANSPORT": "streamable-http",
        "HOST": "127.0.0.1",
        "PORT": "8000",
        "MCP_TOOL_MODE": "intent",
        "ATLASSIANTOOL": "True",
        "ATLASSIAN_ADMINTOOL": "True",
        "ATLASSIAN_AGENT_TOKEN": "your_token_here",
        "ATLASSIAN_AGENT_URL": "http://localhost:8080",
        "ATLASSIAN_AGENT_USER": "[email protected]",
        "ATLASSIAN_API_ACCESSTOOL": "True",
        "ATLASSIAN_BEARER_TOKEN": "your_personal_access_token",
        "ATLASSIAN_CONTROLTOOL": "True",
        "ATLASSIAN_DLPTOOL": "True",
        "ATLASSIAN_OAUTH_TOKEN": "your_3lo_access_token",
        "ATLASSIAN_ORGTOOL": "True",
        "ATLASSIAN_USER_MGMTTOOL": "True",
        "ATLASSIAN_USER_PROVISIONINGTOOL": "True",
        "AUDIENCE": "https://your-instance.atlassian.net",
        "CONFLUENCE_OTHERTOOL": "True",
        "CONFLUENCE_PAGETOOL": "True",
        "CONFLUENCE_SPACETOOL": "True",
        "CONFLUENCE_USERTOOL": "True",
        "DELEGATED_SCOPES": "read:jira-work write:jira-work",
        "JIRA_COMMENTTOOL": "True",
        "JIRA_FIELDTOOL": "True",
        "JIRA_ISSUETOOL": "True",
        "JIRA_OTHERTOOL": "True",
        "JIRA_PROJECTTOOL": "True",
        "JIRA_SCREENTOOL": "True",
        "JIRA_USERTOOL": "True",
        "JIRA_WORKFLOWTOOL": "True",
        "KGTOOL": "True"
      }
    }
  }
}

Alternatively, connect to a pre-deployed Streamable-HTTP instance by url:

{
  "mcpServers": {
    "atlassian-mcp": {
      "url": "http://localhost:8000/atlassian-mcp/mcp"
    }
  }
}

Run a reviewed container image as a least-privilege stdio child (no listener or published port):

docker run -i --rm \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --pids-limit=256 \
  --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \
  -e TRANSPORT=stdio \
  -e MCP_TOOL_MODE=intent \
  -e ATLASSIANTOOL=True \
  -e ATLASSIAN_ADMINTOOL=True \
  -e ATLASSIAN_AGENT_TOKEN=your_token_here \
  -e ATLASSIAN_AGENT_URL=http://localhost:8080 \
  -e [email protected] \
  -e ATLASSIAN_API_ACCESSTOOL=True \
  -e ATLASSIAN_BEARER_TOKEN=your_personal_access_token \
  -e ATLASSIAN_CONTROLTOOL=True \
  -e ATLASSIAN_DLPTOOL=True \
  -e ATLASSIAN_OAUTH_TOKEN=your_3lo_access_token \
  -e ATLASSIAN_ORGTOOL=True \
  -e ATLASSIAN_USER_MGMTTOOL=True \
  -e ATLASSIAN_USER_PROVISIONINGTOOL=True \
  -e AUDIENCE=https://your-instance.atlassian.net \
  -e CONFLUENCE_OTHERTOOL=True \
  -e CONFLUENCE_PAGETOOL=True \
  -e CONFLUENCE_SPACETOOL=True \
  -e CONFLUENCE_USERTOOL=True \
  -e DELEGATED_SCOPES="read:jira-work write:jira-work" \
  -e JIRA_COMMENTTOOL=True \
  -e JIRA_FIELDTOOL=True \
  -e JIRA_ISSUETOOL=True \
  -e JIRA_OTHERTOOL=True \
  -e JIRA_PROJECTTOOL=True \
  -e JIRA_SCREENTOOL=True \
  -e JIRA_USERTOOL=True \
  -e JIRA_WORKFLOWTOOL=True \
  -e KGTOOL=True \
  registry.example.invalid/atlassian-agent@sha256:<digest> atlassian-mcp

For containerized network HTTP, supply an authenticated TLS ingress (or direct server TLS), exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy through the operator-owned deployment profile. The generator does not emit an unauthenticated non-loopback listener.

Auto-generated from the code-read env surface (MCP_TOOL_MODE + package vars) — do not edit.

Additional Deployment Options

atlassian-agent can run as a local stdio process or container, or behind a remote network boundary. The Deployment guide carries the detailed transport contract.

• Local container — launch a reviewed immutable image as a least-privilege stdio child with no listener or published port.
• Remote URL — connect through an operator-supplied authenticated HTTPS ingress. Keep its URL, outbound identity references, trust profile, and exact MCP_ALLOWED_HOSTS in AgentConfig.

---

Environment Variables

Package environment variables

Variable	Example	Description
HOST	0.0.0.0
PORT	8000
TRANSPORT	stdio	options: stdio, streamable-http, sse
ENABLE_OTEL	True
OTEL_EXPORTER_OTLP_ENDPOINT	http://localhost:8080/api/public/otel
OTEL_EXPORTER_OTLP_PUBLIC_KEY	pk-...
OTEL_EXPORTER_OTLP_SECRET_KEY	sk-...
OTEL_EXPORTER_OTLP_PROTOCOL	http/protobuf
EUNOMIA_TYPE	none	options: none, embedded, remote
EUNOMIA_POLICY_FILE	mcp_policies.json
EUNOMIA_REMOTE_URL	http://eunomia-server:8000
ATLASSIAN_AGENT_URL	http://localhost:8080	(ATLASSIAN_{SUITE}_*) override is set.
ATLASSIAN_AGENT_USER	[email protected]
ATLASSIAN_AGENT_TOKEN	your_token_here
ATLASSIAN_TLS_PROFILE	(unset)	Optional runtime TLS profile selector; verification is mandatory
DEBUG	False
PYTHONUNBUFFERED	1
ENABLE_DELEGATION	True	1. OIDC delegation (RFC 8693) — flow the caller's IdP token to Atlassian
OIDC_CONFIG_URL	https://idp.example.com/.well-known/openid-configuration
OIDC_CLIENT_ID	your_client_id
OIDC_CLIENT_SECRET	your_client_secret
AUDIENCE	https://your-instance.atlassian.net
DELEGATED_SCOPES	read:jira-work write:jira-work
ATLASSIAN_OAUTH_TOKEN	your_3lo_access_token	2. 3-Legged OAuth (3LO) bearer token
ATLASSIAN_BEARER_TOKEN	your_personal_access_token	3. Bearer token / Personal Access Token (Server / Data Center) — global
ATLASSIANTOOL	True	MCP tools table (condensed action-routed surface).
ATLASSIAN_ADMINTOOL	True
ATLASSIAN_API_ACCESSTOOL	True
ATLASSIAN_CONTROLTOOL	True
ATLASSIAN_DLPTOOL	True
ATLASSIAN_ORGTOOL	True
ATLASSIAN_USER_MGMTTOOL	True
ATLASSIAN_USER_PROVISIONINGTOOL	True
JIRA_PROJECTTOOL	True
JIRA_USERTOOL	True
JIRA_ISSUETOOL	True
JIRA_COMMENTTOOL	True
JIRA_FIELDTOOL	True
JIRA_SCREENTOOL	True
JIRA_WORKFLOWTOOL	True
JIRA_OTHERTOOL	True
CONFLUENCE_PAGETOOL	True
CONFLUENCE_SPACETOOL	True
CONFLUENCE_USERTOOL	True
CONFLUENCE_OTHERTOOL	True

Inherited agent-utilities variables (apply to every connector)

Variable	Example	Description
MCP_TOOL_MODE	condensed	Tool surface: condensed
MCP_ENABLED_TOOLS	—	Comma-separated tool allow-list
MCP_DISABLED_TOOLS	—	Comma-separated tool deny-list
MCP_ENABLED_TAGS	—	Comma-separated tag allow-list
MCP_DISABLED_TAGS	—	Comma-separated tag deny-list
MCP_CLIENT_AUTH	—	Outbound MCP auth (oidc-client-credentials for fleet calls)
MCP_URL	http://localhost:8000/mcp	URL of the MCP server the agent connects to
PROVIDER	openai	LLM provider for the agent
MODEL_ID	gpt-4o	Model id for the agent
ENABLE_WEB_UI	True	Serve the AG-UI web interface

46 package + 10 inherited variable(s). Auto-generated from .env.example + the shared agent-utilities set — do not edit.

Every variable the server reads. Suite-specific credential variables follow the pattern ATLASSIAN_{SUITE}_{URL|USER|TOKEN|VERIFY|BEARER_TOKEN} and fall back to the shared ATLASSIAN_AGENT_* values when unset — so you can run everything off one credential, or split Jira vs Confluence (and Cloud vs Server/DC) by setting the prefixed variables.

Connection & Credentials — shared fallback

Variable	Description	Default
ATLASSIAN_AGENT_URL	Base Atlassian URL (shared fallback for all suites)	http://localhost:8080
ATLASSIAN_AGENT_USER	Account email / username (basic auth)	—
ATLASSIAN_AGENT_TOKEN	API token (basic auth)	—
ATLASSIAN_TLS_PROFILE	Optional shared runtime TLS profile selector	(unset)

Connection & Credentials — Jira (per-suite overrides)

Variable	Description
ATLASSIAN_JIRA_CLOUD_URL / _USER / _TOKEN / _TLS_PROFILE	Jira Cloud connection, credentials, and optional TLS profile selector
ATLASSIAN_JIRA_CLOUD_BEARER_TOKEN	Jira Cloud bearer token (OAuth/PAT)
ATLASSIAN_JIRA_SERVER_URL / _USER / _TOKEN / _TLS_PROFILE	Jira Server / Data Center connection, credentials, and optional TLS profile selector
ATLASSIAN_JIRA_SERVER_BEARER_TOKEN	Jira Server/DC Personal Access Token (PAT)

Connection & Credentials — Confluence (per-suite overrides)

Variable	Description
ATLASSIAN_CONFLUENCE_CLOUD_URL / _USER / _TOKEN / _TLS_PROFILE	Confluence Cloud connection, credentials, and optional TLS profile selector
ATLASSIAN_CONFLUENCE_CLOUD_BEARER_TOKEN	Confluence Cloud bearer token (OAuth/PAT)
ATLASSIAN_CONFLUENCE_SERVER_URL / _USER / _TOKEN / _TLS_PROFILE	Confluence Server / Data Center connection, credentials, and optional TLS profile selector
ATLASSIAN_CONFLUENCE_SERVER_BEARER_TOKEN	Confluence Server/DC Personal Access Token (PAT)

Connection & Credentials — Admin suites (per-suite overrides)

Each admin suite accepts the same _URL / _USER / _TOKEN / _TLS_PROFILE / _BEARER_TOKEN set, falling back to the shared ATLASSIAN_AGENT_* values: ATLASSIAN_ADMIN_CLOUD_*, ATLASSIAN_API_ACCESS_CLOUD_*, ATLASSIAN_CONTROL_CLOUD_*, ATLASSIAN_DLP_CLOUD_*, ATLASSIAN_ORG_CLOUD_*, ATLASSIAN_USER_MGMT_CLOUD_*, ATLASSIAN_USER_PROVISIONING_CLOUD_*.

Authentication mode

Resolved in priority order (first match wins). The bearer token is sent as Authorization: Bearer <token>; basic auth uses email + API token.

Variable	Auth mode	Notes
ENABLE_DELEGATION	1. OIDC delegation (RFC 8693 token exchange)	Set true to flow the caller's IdP token through to Atlassian
OIDC_CONFIG_URL / OIDC_CLIENT_ID / OIDC_CLIENT_SECRET	OIDC delegation IdP config	Required when delegation is enabled
AUDIENCE	OIDC delegation token audience	Defaults to the resolved URL
DELEGATED_SCOPES	OIDC delegation scopes	read:jira-work write:jira-work
ATLASSIAN_OAUTH_TOKEN	2. 3-Legged OAuth (3LO) bearer token	From the 3LO consent flow
ATLASSIAN_BEARER_TOKEN	3. Bearer token / PAT (global)	Server/DC Personal Access Token; per-suite ATLASSIAN_{SUITE}_BEARER_TOKEN overrides this
ATLASSIAN_AGENT_TOKEN (+ _USER)	4. Basic auth (fallback)	Email + API token

MCP server / transport

Variable	Description	Default
TRANSPORT	stdio, streamable-http, or sse	stdio
HOST	Bind host (HTTP transports)	0.0.0.0
PORT	Bind port (HTTP transports)	8000
MCP_TOOL_MODE	Tool surface: condensed, verbose, or both	condensed
MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS	Comma-separated tool allow/deny list	—
MCP_ENABLED_TAGS / MCP_DISABLED_TAGS	Comma-separated tag allow/deny list	—
DEBUG	Verbose logging	False
PYTHONUNBUFFERED	Unbuffered stdout (recommended in containers)	1

Tool toggles

Each action-routed tool can be disabled individually via its toggle env var (set to false). The full list is in the Available MCP Tools table above (e.g. JIRA_ISSUETOOL, CONFLUENCE_PAGETOOL, ATLASSIAN_ADMINTOOL).

Telemetry & governance

Variable	Description	Default
ENABLE_OTEL	Enable OpenTelemetry export	True
OTEL_EXPORTER_OTLP_ENDPOINT	OTLP collector endpoint	—
OTEL_EXPORTER_OTLP_PUBLIC_KEY / OTEL_EXPORTER_OTLP_SECRET_KEY	OTLP auth keys	—
OTEL_EXPORTER_OTLP_PROTOCOL	OTLP protocol (e.g. http/protobuf)	—
EUNOMIA_TYPE	Authorization mode: none, embedded, remote	none
EUNOMIA_POLICY_FILE	Embedded policy file	mcp_policies.json
EUNOMIA_REMOTE_URL	Remote Eunomia server URL	—

Agent CLI (full [agent] runtime only)

Variable	Description	Default
MCP_URL	URL of the MCP server the agent connects to	http://localhost:8000/mcp
PROVIDER	LLM provider (e.g. openai)	openai
MODEL_ID	Model id (e.g. gpt-4o)	gpt-4o
ENABLE_WEB_UI	Serve the AG-UI web interface	True

See .env.example for a copy-paste starting point.

Agent

This repository features a fully integrated Pydantic AI Graph Agent. It communicates over the Agent Control Protocol (ACP) and interacts seamlessly with the Agent Web UI (AG-UI) and Terminal interface.

Running the Agent CLI

To start the interactive command-line agent:

# Set credentials
export ATLASSIAN_AGENT_URL="your_value"
export ATLASSIAN_AGENT_USER="your_value"
export ATLASSIAN_AGENT_TOKEN="your_value"
export ATLASSIAN_TLS_PROFILE="private-pki"
export DEBUG="your_value"
export PYTHONUNBUFFERED="your_value"

# Run the agent server
atlassian-agent --provider openai --model-id gpt-4o

Docker Compose Orchestration

The following docker/agent.compose.yml configures the Agent, Web UI, and Terminal Interface together:

version: '3.8'

services:
  atlassian-agent-mcp:
    image: example/atlassian-agent:mcp
    container_name: atlassian-agent-mcp
    hostname: atlassian-agent-mcp
    restart: always
    env_file:
      - ../.env
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=8000
      - TRANSPORT=streamable-http
    ports:
      - "8000:8000"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/health')"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 10s
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

  atlassian-agent-agent:
    image: example/atlassian-agent@sha256:<digest>
    container_name: atlassian-agent-agent
    hostname: atlassian-agent-agent
    restart: always
    depends_on:
      - atlassian-agent-mcp
    env_file:
      - ../.env
    command: [ "atlassian-agent" ]
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=9004
      - MCP_URL=http://atlassian-agent-mcp:8000/mcp
      - PROVIDER=${PROVIDER:-openai}
      - MODEL_ID=${MODEL_ID:-gpt-4o}
      - ENABLE_WEB_UI=True
      - ENABLE_OTEL=True
    ports:
      - "9004:9004"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:9004/health')"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 10s
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

Detailed graph node architecture explanations, custom skill configurations, and agentic trace guides are available in docs/deployment.md.

---

Security & Governance

Built directly upon the enterprise-ready agent-utilities core, standard security parameters are fully supported:

Access Control & Policy Enforcement

• Eunomia Policies: Fine-grained, policy-driven tool authorization. Supports none, local embedded (mcp_policies.json), or centralized remote modes.
• OIDC Token Delegation: Compliant with RFC 8693 token exchange for flowing authenticating user credentials from Web UI / ACP → Agent → MCP.
• Scoped Credentials: Execution context runs restricted to the specific caller identity.

Runtime Security Grid

Feature	Functionality	Enablement
Tool Guard	Sensitivity inspection with human-in-the-loop validation	Enabled by default
Prompt Injection Defense	Input scanning, repetition monitoring, and recursive loop blocks	Enabled by default
Context Safety Guard	Stuck-loop detectors and contextual overflow preemptive alerts	Enabled by default

---

Installation

Pick the extra that matches what you want to run:

Extra	Installs	Use when
atlassian-agent[mcp]	Connector-focused MCP server (agent-utilities[mcp] — FastMCP/FastAPI + epistemic-graph[full])	You only run the MCP server (smallest install / image)
atlassian-agent[agent]	Agent runtime (agent-utilities[agent-runtime,logfire] — model orchestration + epistemic-graph[full])	You run the integrated agent
atlassian-agent[all]	Everything (mcp + agent + logfire)	Development / both surfaces

# Connector-focused MCP server (includes the shared graph engine)
uv pip install "atlassian-agent[mcp]"

# Agent runtime (adds model orchestration to the shared graph engine)
uv pip install "atlassian-agent[agent]"

# Everything (development)
uv pip install "atlassian-agent[all]"      # or: python -m pip install "atlassian-agent[all]"

Container images (:mcp vs :agent)

One multi-stage docker/Dockerfile builds two right-sized images, selected by --target:

Image tag	Build target	Contents	Entrypoint
example/atlassian-agent:mcp	--target mcp	atlassian-agent[mcp] — connector-focused, includes epistemic-graph[full]; no model-orchestration stack	atlassian-mcp
example/atlassian-agent@sha256:<digest>	--target agent (default)	atlassian-agent[agent] — agent runtime, model orchestration + epistemic-graph[full]	atlassian-agent

docker build --target mcp   -t example/atlassian-agent:mcp    docker/   # connector-focused MCP server
docker build --target agent -t example/atlassian-agent:agent-local docker/   # agent runtime

docker/mcp.compose.yml runs the connector-focused :mcp server; docker/agent.compose.yml runs the agent (immutable agent digest) with a co-located :mcp sidecar.

Knowledge-graph database (epistemic-graph)

Both [mcp] and [agent] carry the epistemic-graph engine through the required Agent Utilities core dependency (epistemic-graph[full]). The [mcp] extra keeps the server connector-focused; [agent] additionally enables model orchestration. Local deployments can use the bundled engine. For production or shared state, run epistemic-graph as a dedicated database service and configure the runtime to use it. Deployment recipes (single-node + Raft HA), connection configuration, and architecture diagrams are documented in the epistemic-graph deployment guide.

---

Documentation

The complete documentation is published as the official documentation site and is the recommended reference for installation, deployment, and day-to-day operation.

Page	Contents
Installation	pip, source, extras, prebuilt Docker image
Deployment	run the MCP server, the agent server, Compose, Caddy + Technitium, env config
Usage	the MCP tools, the Atlassian Python clients, the CLI
Overview	architecture, enterprise readiness, MCP configuration
Concepts	concept registry (CONCEPT:ATL-*)

---

Repository Owners

---

Contribute

Contributions are welcome! Please ensure code quality by executing local checks before submitting pull requests:

• Format code using ruff format .
• Lint code using ruff check .
• Validate type-safety with mypy .
• Execute test suites using pytest

Deploy with agent-utilities-deployment

Provision this package with the consolidated agent-utilities-deployment workflow. It selects an installed-package, editable-source, or immutable-container path; records only runtime secret and TLS-profile references in AgentConfig; and runs doctor, registration, policy, observability, and rollback gates. Ask your agent to "deploy atlassian-agent with agent-utilities-deployment".

Install mode	Command
Installed package	uv tool install "atlassian-agent[mcp]", then run atlassian-mcp
Editable source	uv pip install -e ".[agent]", then run atlassian-mcp
Immutable container	deploy registry.example.invalid/atlassian-agent@sha256:<digest> through the operator-selected orchestrator

The repository embeds no deployment profile, credential value, certificate path, or environment-specific endpoint. Supply those at runtime through AgentConfig and the configured secret provider.

Governed capability contract

This package ships a compact canonical skill surface with specialist procedures kept as referenced workflows. The current MCP tools, skill metadata, connector_manifest.yml, ontology, mappings, shapes, fixtures, migrations, tool-schema fingerprints, and certification metadata form one versioned capability contract. Validate them together; do not rely on stale tool names or historical per-task skill wrappers.

Runtime endpoints, credentials, certificate trust, tenant identity, retention, and observability policy are deployment inputs and are never packaged values. See Configuration, trust, and privacy before enabling a network transport, connector ingestion, GraphOS delegation, or trace export.