Atlassian MCP for Copilot
Connect VS Code to Jira and optionally Confluence Cloud, Data Center, or Server using separate credentials.
Cloud currently uses API tokens; OAuth is not implemented.
Set up the server
- On first activation, the extension installs its bundled MCP server in the background. It looks for Python 3.11 or newer automatically and asks for its path only if detection fails. pip needs access to a package index for this setup.
- After the server setup completes, enter your Jira or Confluence HTTPS URL. The extension infers the service from recognizable hostnames or paths. If a URL is ambiguous, type Jira or Confluence when asked; a product-specific URL (such as one containing
/wiki for Confluence) avoids this extra question. Atlassian Cloud URLs are detected automatically; other URLs default to Data Center / Server. For Jira Cloud, enter the Atlassian account email, choose whether the token is standard or scoped, and enter its API token. For read access, scoped tokens need Jira scopes that permit reading the current user and issues (for example, read:jira-user and read:jira-work); add the scopes needed for other operations. Data Center / Server requires a personal access token. If VS Code requests a reload to enable the extension, reload the window.
- Use the single Atlassian MCP for Copilot: Connect command in the Command Palette. It asks for a site URL, reuses saved credentials if that URL is already connected, or asks for the credentials needed to add it. Service and Cloud vs. Data Center / Server are inferred from the URL where possible; no saved-connection or deployment picker is shown. For Cloud, choose the API token type that matches the token you created and provide its required scopes.
- After verifying your credentials, the extension asks VS Code to start Atlassian MCP for Copilot automatically. Review any VS Code trust prompt, then choose Open Copilot Chat and ask a question, for example: "Use Atlassian MCP for Copilot to find the five most recently updated issues in PROJECT." No terminal command or
.env file is needed.
The extension checks each service's credentials before saving them separately in VS Code SecretStorage. Saved credentials are retained, but exactly one connection—Jira Cloud, Jira Data Center / Server, or Confluence—is active and available to Copilot at a time. Use Atlassian MCP for Copilot: Connect and enter the saved site's URL to verify and switch to it; if the saved token is rejected, the extension offers to collect and verify a replacement before updating SecretStorage. Entering a new URL starts setup for that service, and a newly verified connection becomes the only active one. If you previously added this server manually, disable the duplicate entry.
VS Code manages the server process. The extension restores only the selected connection when you reopen VS Code; it does not ask for the URL again when credentials are already saved. Existing installs with multiple saved connections prompt once to choose the active one. If initial setup is dismissed, it will be offered again the next time VS Code starts. If tools don't appear, check that MCP access is enabled and use MCP: List Servers in the same window and chat context to check the server status and output. Jira credential verification is separate from MCP tool discovery. Some Copilot sessions may not support editor-provided servers.
The extension starts in read-only mode. To allow changes, enable the user setting secureJiraMcp.allowWrites; the server still refuses changes if the client cannot show its approval prompt. Test both approval and rejection on non-production Jira and Confluence content before enabling writes in production. Confluence page/comment bodies are plain text; attachments use base64 and the configured byte limit. Jira Cloud uses REST API v3; Confluence Cloud uses REST API v1.
Outbound Jira and Confluence connections resolve DNS and connect to the validated IP. Private IPs are accepted automatically only for the exact hostname in the Jira or Confluence URL you configured. Loopback, link-local, and cloud-metadata addresses remain blocked. The optional secureJiraMcp.allowedNetworks setting can allow additional non-global network ranges when required; use only network-team-approved CIDR(s).
The connection flow asks for the site URL first and detects Atlassian Cloud from *.atlassian.net; other URLs default to Data Center / Server. Jira Cloud requires the account email plus either a standard API token or a scoped API token; scoped tokens use Atlassian's Jira API gateway. Choose the token type that matches the token you created. Data Center / Server requires its Personal Access Token. Credentials are saved only after the connection check succeeds. If a check fails, existing saved and active connections are preserved; retry with Atlassian MCP for Copilot: Connect.
Private-network Jira and Confluence sites can connect without CIDR configuration when their URL hostname resolves to a private IP. URL-based deployment detection does not bypass outbound protections; connections remain pinned to resolved addresses and sensitive metadata destinations remain blocked.
If VS Code inherits an HTTPS_PROXY, that proxy resolves the service hostname, so the server cannot pin the destination IP itself. Set secureJiraMcp.trustHttpsProxy only when the proxy is trusted and its egress is restricted. This is an explicit trust trade-off, not an additional Jira or Confluence allowlist.
Updates reuse your saved Jira and Confluence connections and install the matching server when needed. If setup fails, select Show Output for installation diagnostics. Standalone Copilot CLI and browser-only VS Code are not supported by this wrapper.