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.

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": $body.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
• Project tracking recipes
• What agent tokens can and cannot do
• All recipes

Related recipes