tasks_create
Create a task in a project. Tasks are per-project tickets — useful for bugs, todos, or end-user-filed feedback inside your app. Tasks live in the project's own database.
Example:
{
"project_id": "my-saas",
"title": "Fix login redirect",
"description": "After OAuth, users land on /home instead of /dashboard.",
"priority": "high",
"labels": ["bug", "auth"]
}Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>",
"title": "<title>"
},
"name": "tasks_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | Optional subsystem tag (free-form, e.g. "billing", "auth", "ui") for filtering related tasks. | |
| type | No | Defaults to task. Type is a filter; custom labels are supported. vision — why the organization exists. philosophy — a belief guiding trade-offs, including why it matters. directive — a rule or instruction, including what it supersedes. decision — a steer from the person who owns the project: their words, what it changes, what it replaces, the work it governs. sop — how to carry out a recurring job. spec — what to build and its acceptance criteria. roadmap — direction and outcomes for work ahead. epic — a larger outcome grouping related tasks. task — a concrete piece of current work. bug — behavior that needs correction. report — an observation, incident or customer finding. principle — a reusable rule for making decisions. learning — a lesson supported by experience or evidence. supplier — facts about an external service or supplier. content — a draft or plan for published material. policy — a standing rule governing operations. stance — a position on a subject and its reasoning. When the person who owns the project changes direction, parks or picks something, or overrules a plan, record it as a decision the same day, quoting them. | |
| title | Yes | Short summary, required. | |
| due_at | No | Optional Unix timestamp (ms). | |
| labels | No | Tag labels for filtering. The board recognizes explicit opt-ins requires-deployment, requires-smoke-test, and requires-resolution-note as completion guidance. In v1 only requires-deployment has machine-verifiable evidence and blocks close; freeform prose never activates a gate. | |
| status | No | Work records only. Defaults to 'open'. 'backlog' represents untriaged ideas, 'blocked' represents work awaiting external action, and 'needs_review' represents completed work awaiting sign-off. | |
| assignee | No | Free-form assignee (user ID, email, or label). | |
| priority | No | Defaults to 'normal'. | |
| reporter | No | Optional reporter override; defaults to the caller. | |
| template | No | Optional template that fills priority, labels, area, and description with defaults. Caller-provided fields override template defaults; `tasks_templates` exposes each template. | |
| parent_id | No | Optional parent task ID — makes this a sub-task of the given task. | |
| project_id | Yes | Project ID (UUID), subdomain, or slug, resolved server-side; 'default' is the organization's shared task board. | |
| waiting_on | No | Explicit dependency on input or action; explain what is needed in status_note. | |
| attachments | No | sw.fs paths to attach to this task (screenshots, logs, repro files). Each path is a string like "/uploads/screenshot.png" — not a full URL. Max 25 per task. | |
| description | No | Long-form body. | |
| status_note | No | One plain sentence: what is done, next, and blocked. Shown in compact board reads. |