MCP Jira Scoped MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-jira-scoped -- npx -y mcp-jira-scoped

{
  "mcpServers": {
    "mcp-jira-scoped": {
      "args": [
        "-y",
        "mcp-jira-scoped"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-jira-scoped]
command = "npx"
args = ["-y", "mcp-jira-scoped"]

{
  "mcpServers": {
    "mcp-jira-scoped": {
      "args": [
        "-y",
        "mcp-jira-scoped"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-jira-scoped": {
      "args": [
        "-y",
        "mcp-jira-scoped"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: JIRA_INSTANCE (Jira instance name (e.g. 'mycompany' for mycompany.atlassian.net)), JIRA_USER_EMAIL (Email associated with the API token), JIRA_API_TOKEN (Scoped API token from https://id.atlassian.com/manage-profile/security/api-tokens), JIRA_SCOPES (Comma-separated scopes: read:jira-work, write:jira-work, read:jira-user, read:me. Defaults to read:jira-work), JIRA_CLOUD_ID (Atlassian Cloud ID (auto-fetched if not set). Find at https://yoursite.atlassian.net/_edge/tenant_info). The author declared them in the registry entry; get the values from the project itself.