Create a GitHub issue

Let your AI file GitHub issues with a fine-grained PAT it never touches.

Open an issue in a fixed repository through a signed pipe. The fine-grained PAT is scoped to that one repo and lives server-side. Creating is the one operation in this suite that duplicates on retry, which is why it is its own pipe rather than a mode of the update rung: a fire whose receipt you could not read needs a human decision, not an automatic resend. It also asks only for owner and repo, where the GraphQL rungs want an opaque repository node id you would have to look up first. Only title is required; body and labels are optional and may be omitted entirely. One diagnostic worth carrying: GitHub answers a repository the token cannot see with 404 rather than 403, deliberately, so a scope problem and a typo in the repo name look identical in the receipt. Check the PAT's repository access before hunting for a misspelling.

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_github_create_issue

Create an issue in the configured repository. Input: title (required), body, labels[].

Setup walkthrough

1. GITHUB_PAT: GitHub Settings, Developer settings, Fine-grained tokens: generate for ONLY the target repository with Issues read and write. Paste it in the FlurryPORT secret page.

Intent schema

{
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "title": {
      "type": "string",
      "maxLength": 256
    },
    "body": {
      "type": "string"
    },
    "labels": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  }
}

Install-time parameters

owner

install-time: Repository owner (org or user).

repo

install-time: Repository name.

Transformation

{ "title": $body.title, "body": ($exists($body.body) ? $body.body : ""), "labels": ($exists($body.labels) ? $body.labels : []) }

Delivery target

POST https://api.github.com/repos/$install.owner/$install.repo/issues

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

Gotchas

• GitHub requires a User-Agent header on API calls; the pipe sends one for you.
• A 404 from the API usually means the PAT is not granted to that repository: GitHub hides existence rather than answering 403.

Where this fits

• Destination: GitHub
• Part of the GitHub issues suite
• Project tracking recipes
• What agent tokens can and cannot do
• All recipes

Related recipes