@kody/atlassian

@kody/atlassian

Official Atlassian mark. Atlassian®, Jira®, and Confluence® are trademarks of Atlassian Pty Ltd. This package is not affiliated with or endorsed by Atlassian.

Intent

Provide reusable Jira and Confluence helpers that prefer the official Atlassian MCP server (kody.mcp["atlassian"]) so onboarding is add-server-and-authorize, not register-an-OAuth-app. Fall back to the @kody/jira OAuth or API-token helpers when MCP is not connected.

This listing is meant to be forked. After you fork, connect your Atlassian site. Do not treat the live @kody/atlassian connection as yours.

Share this listing as https://kody.codes/@kody/atlassian

What it does

• Probe whether the Atlassian MCP server is connected (or report setup)
• Search Jira issues the authorizing user can already see
• Search Confluence pages the authorizing user can already see
• Prefer official MCP over registering a custom Atlassian OAuth app

Prerequisites / setup

Preferred: add the official Atlassian MCP server, then authorize it.

await kody.mcpServerAdd({
  name: 'atlassian',
  url: 'https://mcp.atlassian.com/v1/mcp/authv2',
})

Open the returned authUrl. Helpers then call kody.mcp["atlassian"]. Do not register an Atlassian OAuth app for the one-click path.

Fallback: use @kody/jira for bring-your-own Atlassian OAuth 2.0 (3LO) or an API token plus account email. See https://kody.codes/@kody/jira

Agents: see AGENTS.md for import paths and smoke checks.

Done when

• Atlassian MCP server atlassian is added and authorized (preferred), or @kody/jira fallback credentials are ready
• Smoke test reports MCP connected (or clear fallback setup guidance)
• Search helpers return issues/pages the user can already see

Branding

community-icon.svg is Atlassian's official mark. Atlassian®, Jira®, and Confluence® are trademarks of Atlassian Pty Ltd. This package is not affiliated with or endorsed by Atlassian.