Skip to content

Jira and Confluence (Atlassian)

Artific Connect · Atlassian gives a key Jira and Confluence Cloud tools: search and change issues, search and change pages, over your own Atlassian site. It installs from the Marketplace like any other bundle.

What you get

One toolset, atlassian, holding eight connectors — five over Jira, three over Confluence — plus a skill that tells the model what a JQL or CQL query looks like and what a transition id is. Every call runs as your organisation's own Atlassian account, not a person's own login: unlike GitHub or Linear, nobody signs in individually here.

Your own site and API token

This bundle asks for two things at install, both your organisation's own:

  • atlassian_site — your Atlassian site, pre-filled with a default you edit by replacing your-site with your own site's subdomain (the part before .atlassian.net) and leaving everything else exactly as shown: https://your-site.atlassian.net. Every one of the eight connectors below adds its own path to this one address — the five Jira ones under /rest/api/3/..., the three Confluence ones under /wiki/... on the same site — so typing it once is enough for the whole bundle.

  • atlassian_credential — your Atlassian account email and an API token, created at id.atlassian.com under Security → API tokens. Supply it as:

{ "type": "basic", "username": "<account email>", "password": "<API token>" }

Until both are supplied the subscription waits at needs configuration. Every value is your own; this deployment registers nothing at Atlassian on your behalf.

Before it works

Your administrator has to allow *.atlassian.net in the key's own egress policy — only your own site, under that glob, is ever reached, because atlassian_site is the only address this bundle ever starts a call from.

The eight tools

Tool Ask it for Give it
api__jira-search matching Jira issues a JQL query
api__jira-get-issue one issue's detail its key, e.g. ENG-123
api__jira-create-issue a new issue a project key, an issue type and a summary
api__jira-add-comment adding a comment the issue's key and the comment text
api__jira-transition moving an issue the issue's key and a transition id (read from the issue first)
api__confluence-search matching Confluence pages a CQL query
api__confluence-get-page one page's content its id
api__confluence-create-page a new page a space id, a title and the body

Good to know

  • Verified 2026-09-24 on developer.atlassian.com: /rest/api/3/... (Basic auth with an API token) is Jira Cloud's own REST v3, and HTTP Basic with an account email and API token is its documented authentication for scripts. Confluence's page reads and writes are on the v2 API (/wiki/api/v2/pages); CQL search still lives on the older v1 API (/wiki/rest/api/search) — Atlassian has not moved it to v2 yet, so this bundle deliberately mixes the two.
  • Verified 2026-09-24: the old GET /rest/api/3/search endpoint Atlassian once documented for JQL is retired (410 Gone since August 2025); this bundle uses the current POST /rest/api/3/search/jql instead.
  • Decided 2026-09-24: this bundle uses REST with an API token rather than Atlassian's own hosted MCP server (mcp.atlassian.com), because whether a third-party application such as Artific's may register an OAuth client against that server was not established; REST with an API token is available to every Atlassian Cloud site today without any registration at Atlassian at all.
  • Every Jira and Confluence project or space still applies its own permissions on top of what the token's account can see; "not found" on an issue or page usually means the account cannot see it.
  • The mark: this bundle's card uses Atlassian's own mark, from its logo download, under the Marketplace Partner brand guidelines, which permit a partner using Atlassian's logo in its own marketing assets (checked 2026-09-24).