First-party app

Jira

Name: Jira
Author: w6w

Create, search and transition Jira issues, and manage comments, users and projects.

stable Project ManagementDeveloper Tools

About

Jira ships in the w6w first-party pack. It declares 15 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.

App id: io.w6w.jira
Version: 0.2.2
Author: w6w
Licence: MIT
Categories: Project Management · Developer Tools

Overview

Jira creates, searches and moves issues through their workflow from outside Jira itself — creating and updating issues, assigning them, and transitioning them between statuses after first reading which transitions are actually available from an issue’s current state, rather than guessing at a status name that may not apply.

Comments are a full create/list/delete surface, and issues can be searched with JQL to find exactly the set a workflow needs to act on rather than paging through everything in a project. Projects and users round it out — both can be listed or looked up individually, and users can be searched by name, which matters for resolving who to assign an issue to.

A fit for filing issues from an external event — a bug report, a support escalation, a form submission — and for moving work through a Jira workflow driven by something happening outside Jira.

Build with Jira

Three routes to the same 15 actions. The Workflow tab is generated from Jira's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Actions Workflow Code MCP

Add Comment

comment-add

Post a comment on an issue, optionally restricted to one role.

Delete Comment

comment-delete

Delete a comment from an issue.

List Comments

comment-get-many

List an issue's comments, oldest first.

Assign Issue

issue-assign

Assign an issue to a user, or leave the account id empty to unassign it.

Create Issue

issue-create

Create an issue in a project.

Delete Issue

issue-delete

Permanently delete an issue. Jira has no trash — prefer transitioning it to Done unless you mean it.

Get Issue

issue-get

Fetch an issue by key or id.

Get Issue Transitions

issue-get-transitions

List the workflow transitions available from the issue's CURRENT status — the ids `issue-transition` needs.

Search Issues (JQL)

issue-search

Run a JQL query and return the matching issues.

Transition Issue

issue-transition

Move an issue through its workflow. Status is not directly writable — use `issue-get-transitions` to find the id.

Update Issue

issue-update

Update an issue's fields. Jira answers 204 with no body — use `issue-get` to read the result back. Changing status is `issue-transition`.

Get Project

project-get

Fetch a project by key or id, including its issue types.

List Projects

project-get-many

List the projects the connection can see — the source of project keys.

Get User

user-get

Fetch a user by Atlassian account id.

Search Users

user-search

Find users by name or email. Returns account ids — the only identifier Jira's API accepts.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Jira's real ids.

{
  "manifestVersion": "2",
  "name": "jira-example",
  "steps": [
    {
      "id": "comment-add",
      "uses": {
        "app": "io.w6w.jira",
        "action": "comment-add",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "issueKey": "<issueKey>",
        "body": "<body>"
      }
    }
  ]
}

Here are some of the things you can do

Add Comment
perform
comment-add
List Comments
search
comment-get-many
Assign Issue
perform
issue-assign
Create Issue
perform
issue-create
Get Issue
read
issue-get

+10 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Jira, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Jira. The Workflow tab is where this app's real ids are.

JS SDK CLI

Install

npm yarn pnpm deno

npm install @w6w/sdk

yarn add @w6w/sdk

pnpm add @w6w/sdk

deno add npm:@w6w/sdk

Code

import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "issue-create",
  payload: {
    projectKey: "<value>",
    issueType: "<value>",
    summary: "<value>",
    // description: "<value>",
    // assigneeId: "<value>",
    // priority: "<value>",
    // labels: "<value>",
    // parentKey: "<value>",
    // additionalFields: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);

Install the CLI

npm install -g @w6w/cli

CLI

w6w run conn_YOUR_CONNECTION_ID --action issue-create --payload '{"projectKey":"<value>","issueType":"<value>","summary":"<value>"}'

Give an AI agent Jira — without giving it Jira's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call

{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.jira#comment-add",
    "input": {
      "issueKey": "<issueKey>",
      "body": "<body>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Jira connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

Jira's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. Jira itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Jira declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Jira platform status

Atlassian Statuspage rollup for jira-software.status.atlassian.com, with per-component detail. Unauthenticated and unsigned.

quota

API quota headroom

dependency

Jira site reachable

Unauthenticated `GET /status` against this connection's Atlassian site — proves the site exists and is serving.