MCP tools

issue_create write

File an issue in a project. Only the project and a title are required, and the milestone is optional, so file the issue when you know where it belongs and place it when you know when. Status defaults to backlog and priority to none. The milestone must belong to the same project as the issue; milestone_list has its ULIDs.

Arguments

NameTypeDescription
assignee_idnull | stringULID of a user; read roadmap://users for the assignable ones
descriptionstringthe body, markdown, at most 65536 characters
labelsnull | arraylabel names or ULIDs to apply; call label_list or read roadmap://labels
milestone_idnull | stringULID of a milestone in the same project; call milestone_list
priorityintegerhow urgent the issue is: 0=none, 1=low, 2=medium, 3=high, 4=urgent One of 0, 1, 2, 3, 4.
project requiredstringthe project key (ENG) or ULID to file the issue in
statusstringthe issue's workflow state, one of: backlog, todo, in_progress, in_review, done, canceled. done and canceled are both terminal One of backlog, todo, in_progress, in_review, done, canceled.
target_datestringwhen the issue is due, as a calendar date YYYY-MM-DD such as 2026-09-01. No time and no timezone. Optional, and in no enforced order with its milestone's or its project's date
title requiredstringa one-line summary, at most 200 characters
typestringthe issue's type, by key such as spec or by ULID; read roadmap://types. Defaults to issue, a work item. A document type (prd, frd, nfr, spec, convention on a fresh workspace) makes the issue a document: owned, read in the reading layout, approved by a person

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "assignee_id": {
      "description": "ULID of a user; read roadmap://users for the assignable ones",
      "type": [
        "null",
        "string"
      ]
    },
    "description": {
      "description": "the body, markdown, at most 65536 characters",
      "type": "string"
    },
    "labels": {
      "description": "label names or ULIDs to apply; call label_list or read roadmap://labels",
      "items": {
        "type": "string"
      },
      "type": [
        "null",
        "array"
      ]
    },
    "milestone_id": {
      "description": "ULID of a milestone in the same project; call milestone_list",
      "type": [
        "null",
        "string"
      ]
    },
    "priority": {
      "description": "how urgent the issue is: 0=none, 1=low, 2=medium, 3=high, 4=urgent",
      "enum": [
        0,
        1,
        2,
        3,
        4
      ],
      "type": "integer"
    },
    "project": {
      "description": "the project key (ENG) or ULID to file the issue in",
      "type": "string"
    },
    "status": {
      "description": "the issue's workflow state, one of: backlog, todo, in_progress, in_review, done, canceled. done and canceled are both terminal",
      "enum": [
        "backlog",
        "todo",
        "in_progress",
        "in_review",
        "done",
        "canceled"
      ],
      "type": "string"
    },
    "target_date": {
      "description": "when the issue is due, as a calendar date YYYY-MM-DD such as 2026-09-01. No time and no timezone. Optional, and in no enforced order with its milestone's or its project's date",
      "type": "string"
    },
    "title": {
      "description": "a one-line summary, at most 200 characters",
      "type": "string"
    },
    "type": {
      "description": "the issue's type, by key such as spec or by ULID; read roadmap://types. Defaults to issue, a work item. A document type (prd, frd, nfr, spec, convention on a fresh workspace) makes the issue a document: owned, read in the reading layout, approved by a person",
      "type": "string"
    }
  },
  "required": [
    "project",
    "title"
  ],
  "type": "object"
}