1. Home
  2. MCP Atlassian
  3. MCP Atlassian for VS Code: Setup & Config

Data as of

MCP Atlassian for VS Code: Setup & Config

MCP Atlassian connects VS Code to Jira and Confluence for issue tracking and team documentation.

MCP Atlassian VS Code configuration

  1. Choose VS Code configuration scope

    For MCP Atlassian, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add MCP Atlassian to VS Code

    Use the mcp-atlassian entry below in servers. Keep MCP Atlassian's documented stdio connection fields and your other VS Code entries.

  3. Check MCP Atlassian in VS Code

    MCP Atlassian: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "mcp-atlassian": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "<your Jira instance URL>",
        "JIRA_USERNAME": "<your Jira account email>",
        "JIRA_API_TOKEN": "<your Jira Cloud API token>",
        "CONFLUENCE_URL": "<your Confluence instance URL>",
        "CONFLUENCE_USERNAME": "<your Confluence account email>",
        "CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
      }
    }
  }
}

MCP Atlassian in VS Code: stdio checks

  • Make uvx mcp-atlassian (from uv, for Python tools) available in the workspace, container, or remote environment hosting MCP Atlassian. Start through VS Code's MCP controls; inspect output and trust prompts.
  • For MCP Atlassian, keep CONFLUENCE_API_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, JIRA_API_TOKEN, JIRA_URL, JIRA_USERNAME out of version control; VS Code documents input variables and secret handling.
  • MCP Atlassian uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
jira_search, jira_get_issue, jira_create_issue

MCP Atlassian — details. VS Code guide

Frequently asked questions

For MCP Atlassian, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's mcp-atlassian example uses stdio.

MCP Atlassian's VS Code configuration invokes uvx mcp-atlassian (from uv, for Python tools).

VS Code's MCP Atlassian example references CONFLUENCE_API_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, JIRA_API_TOKEN, JIRA_URL, JIRA_USERNAME. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

MCP Atlassian's stored list contains 10 tools, including jira_search, jira_get_issue, jira_create_issue. Compare those names with VS Code's connected tool list; the stored list is not a live check.