Create a Jira issue

Let your AI file Jira Cloud issues with an API token it never touches.

Create an issue in a Jira Cloud project via the REST v3 API. The Basic credential (base64 of email:api_token) rides the Authorization header and is resolved server-side at delivery; the site, project, and issue type are fixed at install.

The credential never enters the model context: it lives in the FlurryPORT secret store, deliveries are signed server-side, and every send returns a receipt your agent can quote.

npx flurryport mcp

Tools your agent gains

flry_jira_create_issue

Create a Jira issue in the configured site/project. Input: summary (required), description (required, plain text).

Setup walkthrough

1. JIRA_EMAIL_TOKEN: Create an API token at id.atlassian.com/manage-profile/security/api-tokens. On the scopes screen pick the Jira app and grant a BROAD scope set: the issue-write scopes (write:issue:jira AND write:issue:jira-software for team-managed/Scrum projects) PLUS the project/issue-type/field READ scopes. The create endpoint resolves the project and issue type via reads, so a write-only token returns a misleading 'project doesn't exist or you don't have permission' 400 (and createmeta shows zero projects) even for a site admin on a project that exists. Basic auth wants base64 of your-email:token, NOT the raw token: printf 'you@example.com:YOUR_TOKEN' | base64 (printf, not echo, whose newline 401s it). Paste the base64 into the FlurryPORT secret page; the recipe sends it as Authorization: Basic <value>.

Intent schema

{
  "type": "object",
  "required": [
    "summary",
    "description"
  ],
  "properties": {
    "summary": {
      "type": "string",
      "maxLength": 255
    },
    "description": {
      "type": "string",
      "description": "Plain-text issue description; wrapped into Atlassian Document Format by the recipe."
    }
  }
}

Install-time parameters

site

install-time: Jira Cloud site subdomain; materialized into the API URL.

projectKey

install-time: Project that receives the issues created by this install.

issueType

install-time: Issue type; must match a type the project offers.

Transformation

{ "fields": { "project": { "key": $install.projectKey }, "issuetype": { "name": $install.issueType }, "summary": $body.summary, "description": { "type": "doc", "version": 1, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": $body.description } ] } ] } } }

Delivery target

POST https://$install.site.atlassian.net/rest/api/3/issue

Placeholders like $secrets.NAME resolve server-side at delivery, never in the agent.

Gotchas

• REST v3 requires the description in Atlassian Document Format, not a plain string; the transformation wraps your text into a minimal ADF paragraph for you.
• Basic auth is base64(email:api_token), not the raw token; building it with echo adds a trailing newline that 401s, so use printf.
• Scoped API tokens need a BROAD scope set: create resolves the project and issue type via reads, so a token with only issue-write scopes returns a misleading 'project does not exist' 400 and an empty createmeta, even for a site admin.
• Team-managed (default Scrum) projects need the -software scope variants.
• issueType and projectKey are case-sensitive; success is 201 with the created key.

Where this fits

• Destination: Jira
• Project tracking recipes
• What agent tokens can and cannot do
• All recipes

Related recipes