Repository navigation
Expand file tree
/
Copy path.env.example
More file actions
439 lines (385 loc) · 23.2 KB
/
Copy path.env.example
File metadata and controls
439 lines (385 loc) · 23.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
# MCP-ATLASSIAN CONFIGURATION EXAMPLE
# -------------------------------------
# Copy this file to .env and fill in your details.
# - Do not use double quotes for string values in this file, unless the value itself contains spaces.
# =============================================
# ESSENTIAL ATLASSIAN INSTANCE URLS
# =============================================
# REQUIRED: Replace with your Atlassian instance URLs.
# Example Cloud: https://your-company.atlassian.net
# Example Server/DC: https://jira.your-internal-domain.com
JIRA_URL=https://your-company.atlassian.net
# Example Cloud: https://your-company.atlassian.net/wiki
# Example Server/DC: https://confluence.your-internal-domain.com
CONFLUENCE_URL=https://your-company.atlassian.net/wiki
# =============================================
# AUTHENTICATION: CHOOSE ONE METHOD PER PRODUCT (Jira/Confluence)
# =============================================
# mcp-atlassian will attempt to auto-detect the auth method based on the credentials you provide below.
# Precedence for auto-detection:
# 1. OAuth Standard (if Client ID/Secret are set — Cloud with cloud_id, DC without)
# 2. OAuth BYOT (if access token is set — Cloud with cloud_id, DC without)
# 3. Username/API Token (Basic Auth) - Recommended for Cloud
# 4. Personal Access Token (if URL is Server/DC and PAT or *_PERSONAL_TOKEN_COMMAND is set)
# 5. ATLASSIAN_OAUTH_ENABLE=true (minimal BYOT — tokens provided per-request)
# --- METHOD 1: API TOKEN (Recommended for Atlassian Cloud) ---
# Get API tokens from: https://id.atlassian.com/manage-profile/security/api-tokens
# This is the simplest and most reliable authentication method for Cloud deployments.
JIRA_API_TOKEN=your_jira_api_token_here
CONFLUENCE_API_TOKEN=your_confluence_api_token_here
# --- DEFERRED CREDENTIALS (Optional) ---
# Instead of setting a token directly, set its *_COMMAND variant to run a
# command lazily on first use. API token commands still need the matching
# *_USERNAME; personal token commands are for Server/DC only.
# The command's stdout (trimmed) is used as the token value.
# If the plain env var is also set, the command variant is ignored.
# Commands run without an implicit shell. Invoke sh -c explicitly if needed.
# Stdin is closed, so helpers must not read from it (they would otherwise
# consume the MCP stdio transport).
# On Server/DC, *_PERSONAL_TOKEN_COMMAND outranks static username/API-token
# basic auth; if the command fails, the static credentials are used instead.
# On Windows the command is parsed by CreateProcess: use double quotes, and
# prefix .bat/.cmd/PowerShell helpers with cmd /c or powershell -NoProfile.
#JIRA_API_TOKEN_COMMAND=gopass show -o my/jira/token
#JIRA_PERSONAL_TOKEN_COMMAND=op read "op://Vault/Jira PAT/credential"
#CONFLUENCE_API_TOKEN_COMMAND=gopass show -o my/confluence/token
#CONFLUENCE_PERSONAL_TOKEN_COMMAND=op read "op://Vault/Confluence PAT/credential"
#CREDENTIAL_COMMAND_TIMEOUT=30 # positive integer seconds (default: 30)
# --- METHOD 2: PERSONAL ACCESS TOKEN (PAT) (Server / Data Center - Recommended) ---
# Create PATs in your Jira/Confluence profile settings (usually under "Personal Access Tokens").
#JIRA_PERSONAL_TOKEN=your_jira_personal_access_token
#CONFLUENCE_PERSONAL_TOKEN=your_confluence_personal_access_token
# --- METHOD 3: USERNAME/PASSWORD (Server / Data Center - Uses Basic Authentication) ---
#JIRA_USERNAME=your_server_dc_username
#JIRA_API_TOKEN=your_jira_server_dc_password # For Server/DC Basic Auth, API_TOKEN holds the actual password
#CONFLUENCE_USERNAME=your_server_dc_username
#CONFLUENCE_API_TOKEN=your_confluence_server_dc_password
# --- METHOD 4: OAUTH 2.0 (Advanced - Cloud and Data Center) ---
# OAuth 2.0 provides enhanced security but is more complex to set up.
# For most users, Method 1 (API Token) is simpler and sufficient.
#
# --- Cloud OAuth 2.0 (3LO) ---
# 1. Create an OAuth 2.0 (3LO) app in Atlassian Developer Console:
# https://developer.atlassian.com/console/myapps/
# 2. Set the Callback/Redirect URI in your app (e.g., http://localhost:8080/callback).
# 3. Grant necessary scopes (see ATLASSIAN_OAUTH_SCOPE below).
# 4. Run 'mcp-atlassian --oauth-setup -v' (or 'uvx mcp-atlassian@latest --oauth-setup -v').
# This wizard will guide you through authorization and provide your ATLASSIAN_OAUTH_CLOUD_ID.
# Tokens are stored securely (keyring or a local file in ~/.mcp-atlassian/).
# Required for --oauth-setup and for the server to use OAuth:
#ATLASSIAN_OAUTH_CLIENT_ID=your_oauth_client_id
#ATLASSIAN_OAUTH_CLIENT_SECRET=your_oauth_client_secret
#ATLASSIAN_OAUTH_REDIRECT_URI=http://localhost:8080/callback # Must match your app's redirect URI
#ATLASSIAN_OAUTH_SCOPE=read:jira-work write:jira-work read:jira-user read:confluence-space.summary read:confluence-content.summary read:confluence-content.all write:confluence-content search:confluence read:page:confluence offline_access # IMPORTANT: 'offline_access' is crucial for refresh tokens
#ATLASSIAN_OAUTH_PROXY_ENABLE=true # Enables MCP OAuth proxy + DCR + /.well-known routes (default: false)
#PUBLIC_BASE_URL=https://mcp.example.com/mcp-atlassian # Public URL where clients reach this server
#ATLASSIAN_OAUTH_ALLOWED_CLIENT_REDIRECT_URIS=http://localhost:*,http://127.0.0.1:*,https://chatgpt.com/connector_platform_oauth_redirect
#ATLASSIAN_OAUTH_ALLOWED_GRANT_TYPES=authorization_code,refresh_token
#ATLASSIAN_OAUTH_REQUIRE_CONSENT=true
# Required for the server AFTER running --oauth-setup (this ID is printed by the setup wizard):
#ATLASSIAN_OAUTH_CLOUD_ID=your_atlassian_cloud_id_from_oauth_setup
# --- Data Center OAuth 2.0 ---
# For Server/DC instances, configure OAuth via your instance's Application Links.
# Service-specific env vars override the global ATLASSIAN_OAUTH_* vars.
#JIRA_OAUTH_CLIENT_ID=your_jira_dc_oauth_client_id
#JIRA_OAUTH_CLIENT_SECRET=your_jira_dc_oauth_client_secret
#CONFLUENCE_OAUTH_CLIENT_ID=your_confluence_dc_oauth_client_id
#CONFLUENCE_OAUTH_CLIENT_SECRET=your_confluence_dc_oauth_client_secret
# --- METHOD 5: BRING YOUR OWN TOKEN (BYOT) OAUTH (Advanced) ---
# Use this method when you have an externally managed OAuth access token.
# This is useful for integration with larger systems (e.g., MCP Gateway) that manage OAuth tokens.
# No token refresh will be performed - the external system is responsible for token management.
#
# Cloud BYOT (requires cloud_id):
#ATLASSIAN_OAUTH_CLOUD_ID=your_atlassian_cloud_id
#ATLASSIAN_OAUTH_ACCESS_TOKEN=your_pre_existing_oauth_access_token
#
# Data Center BYOT (uses instance URL from JIRA_URL/CONFLUENCE_URL):
#JIRA_OAUTH_ACCESS_TOKEN=your_dc_oauth_access_token
#CONFLUENCE_OAUTH_ACCESS_TOKEN=your_dc_oauth_access_token
#
# Minimal BYOT mode — enables OAuth without any credentials or URLs.
# The external system (e.g., MCP Gateway) provides tokens per-request via headers.
#ATLASSIAN_OAUTH_ENABLE=true
# --- METHOD 7: EXTERNAL SESSION PASSTHROUGH (Advanced — proxy-managed auth) ---
# Use this method when an upstream authentication proxy (e.g., an API gateway or
# sidecar) injects session/auth headers into every request before they reach the MCP
# server. The MCP server forwards those headers verbatim to Jira/Confluence and adds
# NO Authorization header of its own.
#
# Required environment variables:
# ATLASSIAN_EXTERNAL_AUTH_ENABLE=true — activates the mode
# IGNORE_HEADER_AUTH=true — prevents the MCP from trying to parse
# Authorization headers as user credentials
# JIRA_PASSTHROUGH_HEADERS=<name> — comma-separated list of header names that
# CONFLUENCE_PASSTHROUGH_HEADERS=<name> the proxy injects (e.g. Cookie, X-Auth-Token)
#
# URL configuration (choose one):
# a) Set JIRA_URL / CONFLUENCE_URL server-side as usual, OR
# b) Let the trusted gateway supply the URL per-request via the
# X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers # trufflehog:ignore (header names only, no secret)
# (useful for multi-tenant / dynamic routing scenarios). This option also
# requires MCP_ALLOWED_URL_DOMAINS so trusted auth headers cannot be sent to
# an attacker-controlled public host.
#
# Behaviour when no passthrough header is present on a request:
# The request is forwarded without an Authorization header; the upstream API
# will return 401, which is propagated back to the MCP client.
#
#ATLASSIAN_EXTERNAL_AUTH_ENABLE=true
#IGNORE_HEADER_AUTH=true
#JIRA_PASSTHROUGH_HEADERS=Cookie
#CONFLUENCE_PASSTHROUGH_HEADERS=Cookie
#MCP_ALLOWED_URL_DOMAINS=atlassian.net
# =============================================
# SERVER/DATA CENTER SPECIFIC SETTINGS
# =============================================
# Only applicable if your JIRA_URL/CONFLUENCE_URL points to a Server/DC instance (not *.atlassian.net).
# Default is true. Set to false if using self-signed certificates (not recommended for production environments).
# Note: Enterprise CA certificates in the OS trust store are trusted automatically via truststore.
#JIRA_SSL_VERIFY=true
#CONFLUENCE_SSL_VERIFY=true
# Set to false to disable OS trust store integration and use the bundled certifi CA bundle instead.
#MCP_ATLASSIAN_USE_SYSTEM_TRUSTSTORE=true
# --- CLIENT CERTIFICATE AUTHENTICATION (mTLS) ---
# For mutual TLS authentication with Server/DC instances.
# Provide either a combined cert/key PEM in *_CLIENT_CERT, or provide
# separate certificate and private key PEM files with *_CLIENT_KEY.
# This is typically used in corporate environments with strict security requirements.
#JIRA_CLIENT_CERT=/path/to/jira-client-cert.pem
#JIRA_CLIENT_KEY=/path/to/jira-client-key.pem
#JIRA_CLIENT_KEY_PASSWORD=password_for_encrypted_key # Not supported by requests; decrypt the key first
#CONFLUENCE_CLIENT_CERT=/path/to/confluence-client-cert.pem
#CONFLUENCE_CLIENT_KEY=/path/to/confluence-client-key.pem
#CONFLUENCE_CLIENT_KEY_PASSWORD=password_for_encrypted_key # Not supported by requests; decrypt the key first
# =============================================
# OPTIONAL CONFIGURATION
# =============================================
# --- General Server Settings ---
# Transport mode for the MCP server. Default is 'stdio'.
# Options: stdio, sse
#TRANSPORT=stdio
# Port for 'sse' transport. Default is 8000.
#PORT=8000
# Host for 'sse' transport. Default is '0.0.0.0'.
#HOST=0.0.0.0
# --- Server TLS (HTTPS listener) ---
# Serve the 'sse'/'streamable-http' transports over HTTPS by terminating TLS at
# the MCP server itself. Point these at a certificate + private key (PEM).
# NOTE: this is the SERVER's own listener cert — the opposite direction from the
# client-side *_CLIENT_CERT mTLS options above (which authenticate the server TO
# Atlassian). Both must be set together; setting only one, or setting either to
# an empty string, aborts startup (empty is treated as a configuration error,
# not as "TLS off"). Under 'stdio' transport they are ignored (no network
# listener). Useful for end-to-end TLS where the certificate is mounted into
# the container from a Secret. The key must be UNENCRYPTED (no passphrase
# support), and the pair is loaded once at startup — rotation requires a
# process restart.
# REQUIRES MCP_ATLASSIAN_USE_SYSTEM_TRUSTSTORE=false (as a real env var or in
# the default .env; --env-file is loaded too late): the OS trust store
# injection is client-side only and would reject every inbound TLS handshake,
# so startup aborts if both are enabled. See the HTTP transport docs for the
# outbound private-CA setup that replaces the OS trust store.
#MCP_SSL_CERTFILE=/path/to/server-cert.pem
#MCP_SSL_KEYFILE=/path/to/server-key.pem
# --- Outbound private CA bundle ---
# Verify Jira/Confluence certificates against this CA bundle (PEM file or
# OpenSSL hashed CA directory) instead of the default CAs. Applies to every auth
# mode, including PAT and OAuth sessions. CURL_CA_BUNDLE is used only when
# REQUESTS_CA_BUNDLE is unset. The bundle replaces the defaults, so include the
# public roots if you also talk to Atlassian Cloud. A path that is not an
# existing file or directory makes the Jira/Confluence client fail to start
# (the path is logged server-side). Ignored when *_SSL_VERIFY=false. For the
# OAuth proxy paths (httpx), also set SSL_CERT_FILE to the same bundle.
#REQUESTS_CA_BUNDLE=/path/to/ca-bundle.pem
#CURL_CA_BUNDLE=/path/to/ca-bundle.pem
#SSL_CERT_FILE=/path/to/ca-bundle.pem
# --- HTTP Timeout ---
# Timeout in seconds for HTTP requests to Atlassian APIs. Default is 75 seconds.
#JIRA_TIMEOUT=75
#CONFLUENCE_TIMEOUT=75
# --- Multi-user token validation cache ---
# Cache successful credential validation across HTTP requests. Set TTL to 0 to
# disable the cache. Default TTL is 300 seconds and default maximum size is 100.
#MCP_ATLASSIAN_VALIDATION_CACHE_TTL=300
#MCP_ATLASSIAN_VALIDATION_CACHE_MAXSIZE=100
# --- HTTP Hardening (Advanced) ---
# Optional safeguards for overloaded Atlassian instances. Read requests are
# retried up to 3 times by default; the other safeguards are disabled unless
# set here.
# Retries cover 429/502/503/504 and connection errors on GET/HEAD/OPTIONS.
# Set ATLASSIAN_RETRY_TOTAL=0 to disable retries. Set
# ATLASSIAN_RETRY_INCLUDE_WRITES=true only if your write endpoints are known to
# be idempotent.
#ATLASSIAN_RETRY_TOTAL=3
#ATLASSIAN_RETRY_BACKOFF=1.0
#ATLASSIAN_RETRY_INCLUDE_WRITES=false
# Retry-After is honored up to this many seconds, and a wait is never shorter
# than the exponential backoff, so `Retry-After: 0` cannot cause a tight loop.
#ATLASSIAN_RETRY_MAX_RETRY_AFTER=60
# Ignore the server's Retry-After header and always use exponential backoff.
#ATLASSIAN_RETRY_IGNORE_RETRY_AFTER=false
#ATLASSIAN_MAX_CONCURRENT_REQUESTS=4
#ATLASSIAN_REQUESTS_PER_SECOND=5
#ATLASSIAN_MAX_PAGINATION_LIMIT=100
#ATLASSIAN_CIRCUIT_BREAKER_THRESHOLD=5
#ATLASSIAN_CIRCUIT_BREAKER_COOLDOWN=30
# --- Jira Fetcher Concurrency ---
# Maximum concurrent Jira fetcher calls offloaded to worker threads. Default is 8.
#JIRA_FETCHER_MAX_WORKERS=8
# --- Read-Only Mode ---
# Disables all write operations (create, update, delete). Default is false.
#READ_ONLY_MODE=false
# --- Server-side file paths ---
# Directory that confines file paths passed to tools (attachment uploads,
# content_file, attachment downloads). Unset: the working directory for stdio,
# ~/.mcp-atlassian/files for sse/streamable-http. Remote transports refuse to
# start when this is / or a home directory.
#MCP_ATLASSIAN_FILES_DIR=/srv/mcp-atlassian/files
# --- Ignore Proxy Auth Headers ---
# Set to 'true' to ignore Authorization headers from reverse proxies
# (e.g., GCP Cloud Run, AWS ALB). When enabled, the server uses only
# environment-configured credentials, ignoring any proxy-injected headers.
# Also required when using ATLASSIAN_EXTERNAL_AUTH_ENABLE=true (external session
# passthrough mode), where the proxy injects auth headers via PASSTHROUGH_HEADERS.
#IGNORE_HEADER_AUTH=true
# --- Host/Origin checks (sse, streamable-http) ---
# With ALLOW_GLOBAL_CRED_FALLBACK=true or IGNORE_HEADER_AUTH=true, a request
# that carries an Origin header must come from a localhost origin or one listed
# in FASTMCP_HTTP_ALLOWED_ORIGINS (403 otherwise), on every address. Requests
# without Origin (MCP clients, proxies) pass. Requests that arrive on a loopback
# address must also carry a localhost Host (421 otherwise). Other deployments
# keep FastMCP's default (no check). Set 'true' to check Host on every address
# and list the hostnames clients and proxies use (JSON lists). Set 'false' to
# turn the checks off.
#FASTMCP_HTTP_HOST_ORIGIN_PROTECTION=true
#FASTMCP_HTTP_ALLOWED_HOSTS=["mcp.example.com"]
#FASTMCP_HTTP_ALLOWED_ORIGINS=["https://mcp.example.com"]
# --- Logging Verbosity ---
# MCP_VERBOSE=true # Enables INFO level logging (equivalent to 'mcp-atlassian -v')
# MCP_VERY_VERBOSE=true # Enables DEBUG level logging (equivalent to 'mcp-atlassian -vv')
# MCP_LOGGING_STDOUT=true # Enables logging to stdout (logging.StreamHandler defaults to stderr)
# Default logging level is WARNING (minimal output).
# --- Tool Filtering ---
# Comma-separated list of tool names to enable. If not set, all tools within
# the active toolsets are enabled (subject to read-only mode and configured services).
# Note: TOOLSETS filtering also applies — a tool must pass both filters.
# Example: ENABLED_TOOLS=confluence_search,jira_get_issue
#ENABLED_TOOLS=
# --- Toolset Filtering ---
# Group-level tool filtering. Toolsets group related tools together.
# Keywords: "all" (all toolsets), "default" (core toolsets only)
# Core toolsets: jira_issues, jira_fields, jira_comments, jira_transitions,
# confluence_pages, confluence_comments
# Example: TOOLSETS=default # Only core tools (~35 tools)
# Example: TOOLSETS=default,jira_agile # Core + agile tools
# Example: TOOLSETS=all # All 25 toolsets (98 tools)
# If unset, all toolsets are enabled (98 tools). Set TOOLSETS=all explicitly to
# preserve this behavior — in v0.22.0, the default will change to core toolsets only.
# Unknown names are silently ignored; if ALL names are unknown, no tools are enabled (fail-closed).
#TOOLSETS=
# --- Content Filtering ---
# Optional: Comma-separated list of Confluence space keys to limit searches and other operations to.
#CONFLUENCE_SPACES_FILTER=DEV,TEAM,DOC
# Optional: Comma-separated list of Jira project keys to limit searches and other operations to.
#JIRA_PROJECTS_FILTER=PROJ,DEVOPS
# --- Jira Key Validation ---
# Regexes the Jira tools use to validate the `issue_key` / `project_key`
# arguments. Override them if your Jira uses a key format the defaults below
# reject, e.g. keys starting with a digit ([A-Z0-9] instead of [A-Z] accepts
# 4ME-123). An invalid regex is ignored and the default is kept.
#JIRA_ISSUE_KEY_PATTERN=^[A-Z][A-Z0-9_]+-\d+(?:-\d+)*$
#JIRA_PROJECT_KEY_PATTERN=^[A-Z][A-Z0-9_]+$
# --- Confluence Cloud attachment download workaround ---
# Confluence Cloud removed the legacy /download/attachments/... endpoint that an
# attachment's `_links.download` still points to; it now returns 401 for
# API-token / scoped-token auth (metadata endpoints keep working). Controls
# whether attachment/image downloads use the v1 REST endpoint
# (/rest/api/content/{id}/child/attachment/{aid}/download) instead:
# unset (default) -> auto: v1 on Cloud, legacy link on Server/DC
# true -> always v1
# false -> always the legacy link
#CONFLUENCE_ATTACHMENT_DOWNLOAD_USE_V1=true
# --- Hierarchy Link Classification ---
# Extend the built-in hierarchy link phrases for issue tree and project
# analysis tools. Format: comma-separated "parent:<phrase>" or "child:<phrase>".
# "parent" means the target issue is the child; "child" means the target is the parent.
# Built-in phrases (always active): is parent of, parent, contains, split to, epic,
# is child of, is contained by, split from.
# Example: HIERARCHY_LINK_PHRASES=parent:rolls up to,child:is part of
#HIERARCHY_LINK_PHRASES=
# Optional: Comma-separated list of JSM/Service Desk project keys where
# jira_add_comment/jira_edit_comment enforce internal-only (non-customer-visible)
# comments server-side. add_comment rejects any call where public is not exactly
# false; edit_comment rejects edits to comments that are currently public;
# transition comments (jira_transition_issue) and issue-link comments
# (jira_create_issue_link) are rejected when they touch a listed project.
# Worklog comments are intentionally NOT guarded (not portal-visible on JSM).
# Unset/empty = feature disabled, zero behavior change.
# NOTE: listing a NON-JSM project key hard-blocks all comment automation on it
# (only public=false is accepted, and the ServiceDesk API 404s on non-JSM issues).
#JIRA_INTERNAL_ONLY_PROJECTS=CC
# --- SLA Metrics Configuration ---
# Configure how SLA metrics are calculated for Jira issues.
# Default metrics to calculate (comma-separated).
# Available: cycle_time, lead_time, time_in_status, due_date_compliance, resolution_time, first_response_time
#JIRA_SLA_METRICS=cycle_time,time_in_status
# Enable working hours filtering (only count business hours, exclude weekends).
#JIRA_SLA_WORKING_HOURS_ONLY=false
# Working hours start time in 24-hour format (HH:MM).
#JIRA_SLA_WORKING_HOURS_START=09:00
# Working hours end time in 24-hour format (HH:MM).
#JIRA_SLA_WORKING_HOURS_END=17:00
# Working days as comma-separated integers (1=Monday, 7=Sunday).
#JIRA_SLA_WORKING_DAYS=1,2,3,4,5
# Timezone for SLA calculations (IANA timezone identifier).
# Examples: UTC, America/New_York, Europe/London, Asia/Tokyo
#JIRA_SLA_TIMEZONE=UTC
# --- Proxy Configuration (Advanced) ---
# Global proxy settings (applies to both Jira and Confluence unless overridden by service-specific proxy settings below).
#HTTP_PROXY=http://proxy.example.com:8080
#HTTPS_PROXY=https://user:[email protected]:8443 # Credentials can be included
#SOCKS_PROXY=socks5://proxy.example.com:1080 # Requires 'requests[socks]' to be installed
#NO_PROXY=localhost,127.0.0.1,.internal.example.com # Comma-separated list of hosts/domains to bypass proxy
# PAC/WPAD proxy auto-configuration is opt-in and only used when no explicit proxy is configured.
#ATLASSIAN_PROXY_WPAD_ENABLE=false
#ATLASSIAN_PROXY_WPAD_URL=http://wpad/wpad.dat
# Jira-specific proxy settings (these override global proxy settings for Jira requests).
#JIRA_HTTP_PROXY=http://jira-proxy.example.com:8080
#JIRA_HTTPS_PROXY=https://jira-proxy.example.com:8443
#JIRA_SOCKS_PROXY=socks5://jira-proxy.example.com:1080
#JIRA_NO_PROXY=localhost,127.0.0.1,.internal.jira.com
#JIRA_PROXY_WPAD_ENABLE=false
#JIRA_PROXY_WPAD_URL=http://jira-wpad.example.com/wpad.dat
# Confluence-specific proxy settings (these override global proxy settings for Confluence requests).
#CONFLUENCE_HTTP_PROXY=http://confluence-proxy.example.com:8080
#CONFLUENCE_HTTPS_PROXY=https://confluence-proxy.example.com:8443
#CONFLUENCE_SOCKS_PROXY=socks5://confluence-proxy.example.com:1080
#CONFLUENCE_NO_PROXY=localhost,127.0.0.1,.internal.confluence.com
#CONFLUENCE_PROXY_WPAD_ENABLE=false
#CONFLUENCE_PROXY_WPAD_URL=http://confluence-wpad.example.com/wpad.dat
# --- SSRF Protection (Advanced) ---
# Optional: Comma-separated list of allowed URL domains for header-based authentication.
# When set, only URLs matching these domains (exact or subdomain) are accepted
# from X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url headers.
# Hosts under allowlisted domains may resolve to private-network addresses
# (on-prem instances), but never to loopback, link-local or cloud-metadata
# addresses. Header-based PAT requests forward *_PASSTHROUGH_HEADERS only to
# JIRA_URL/CONFLUENCE_URL hosts or allowlisted domains, and only these hosts
# may use the configured HTTP(S) proxy. Service credentials and custom headers
# are sent only to the service host or allowlisted domains; list an alternate
# Jira/Confluence base URL here if attachment links point at another host.
# Only list domains you trust.
# Example: MCP_ALLOWED_URL_DOMAINS=atlassian.net,jira.corp.example.com
#MCP_ALLOWED_URL_DOMAINS=
# --- Custom HTTP Headers (Advanced) ---
# Jira-specific custom headers.
#JIRA_CUSTOM_HEADERS=X-Jira-Service=mcp-integration,X-Custom-Auth=jira-token,X-Forwarded-User=service-account
# Jira-specific incoming MCP request header names to pass through.
#JIRA_PASSTHROUGH_HEADERS=X-SSO-User,X-Request-ID
# Confluence-specific custom headers.
#CONFLUENCE_CUSTOM_HEADERS=X-Confluence-Service=mcp-integration,X-Custom-Auth=confluence-token,X-ALB-Token=secret-token
# Confluence-specific incoming MCP request header names to pass through.
#CONFLUENCE_PASSTHROUGH_HEADERS=X-SSO-User,X-Request-ID