"How to create tasks or issues in Jira" matching MCP tools:

• create_standalone_tasksA

  mFlowA

  Create up to 50 tasks in one standalone project in a single call, optionally as a hierarchy — use this instead of create_standalone_task when breaking a plan into several tasks. To nest tasks in the same call, give the parent a localRef (any label unique within the call) and each child a parentRef with that label; parentId instead points at an already-existing task. Validation is all-or-nothing: if any task is invalid (unknown status/label/parent, unresolved or cyclic parentRef, duplicate localRef, missing title) NOTHING is created and every task gets a per-item result. Otherwise tasks are created parents-first in input order and appended to their status column in that order; if one fails mid-batch its children are skipped, never created orphaned. Returns {created, failed, rejected, results: [{index, localRef?, ok, taskId?, key?, error?}]} in input order. Not idempotent: if the call times out or errors, call list_standalone_tasks to see what already exists before retrying, or you will create duplicates.

  ConnectorOAuth

• poker.game.tasks.listA

  retroA

  Returns the tasks of a poker game with their estimate, individual votes, tracker key and link. needs_sync tells whether the agreed estimate still differs from the one stored in the tracker — feed those tasks to poker.game.task.sync. Filter with estimated to see what is done or what is left.

  ConnectorNo auth

• bulk_create_tasksA

  OnplanaB

  Add a list of up to 50 tasks to an existing Onplana project in one call, at the project root or under a sprint / epic. Fits "add these tasks to my launch project" or a checklist pasted into the chat. Single transaction (all-or-nothing), in place of calling create_task N times; add_subtasks covers new tasks that are children of an existing task. THIS TOOL DOES NOT SCHEDULE. Tasks land with NO dates unless startDate and dueDate are set on each one, and there is no way to express durations or predecessors here at all. A schedule (phase durations, effort estimates, "task 5 depends on task 3", a critical path) sent through this tool arrives as a flat dateless list, and the Gantt, timeline and critical path are all empty. Use instantiate_plan instead, which takes estimatedDays per task and computes real start and due dates from them. It accepts a projectId, so it works on a project that already exists. Neither tool accepts predecessors: create the tasks first, then add each dependency with link_dependency. The result includes `url` for the project (and one per task). ALWAYS show the project link in your reply so the user can open what you just created.

  ConnectorOAuth

• get_day_briefA

  AimgodA

  One read for planning or reviewing a day: the day's tasks in display order (timed first), tasks left open the day before, repeating tasks due that day with their streak (streak_today on other days), and planned vs done for that week (Monday to Sunday). Fits for reading a day without showing it: reviewing how a day went, or answering a question about it. When the user wants to see or plan their day, show_day fits. Omit date for the user's today.

  ConnectorOAuth

• acc_create_issueA

  ACC MCPA

  Create a new ACC issue (field observation, coordination clash, safety, quality, etc.) in the target project via the APS Construction Issues API. When to use: The user wants to log a new issue — e.g. 'open a high-priority issue about the leaking valve on level 3' or a downstream agent detected a defect during a model review and needs to record it for the project team. When NOT to use: Do not use to modify an existing issue (use acc_update_issue) and do not use for RFIs (use acc_create_rfi). APS scopes: data:read data:write account:read. Rate limits: ACC Issues API limited to ~100 req/min per app; APS default ~50 req/min per endpoint — batch creations with backoff. Errors: 401 (APS token expired — refresh); 403 (user lacks 'Create Issues' permission on the project or scope insufficient — surface to user); 404 (project_id not found — verify the 'b.' prefix and that the project belongs to a hub the app can see via acc_list_projects); 422 (validation — required field like title/description missing or priority enum invalid); 429 (rate limit — retry after 60s); 5xx (ACC upstream — retry with jitter, do not double-create). Side effects: Creates a persistent issue record visible to all project members. NOT idempotent — a retry on a 5xx may create duplicates; dedupe by title before retrying.

  ConnectorNo auth

• issue_api_keyA

  ThinAir GeoA

  Get the link to create a ThinAir GEO (geocoding/routing) API key. Returns console_url (the signed-in ThinAir Geo console) and instructions; it does NOT return a key and does not create, rotate or revoke any key. The owner signs in, creates the key there and sees it once in their own browser, then sends it as an Authorization: Bearer header. Existing keys keep working. Counts as 1 query against your daily quota. NOTE: keys created there work ONLY against ThinAir Geo — they do NOT authenticate against ThinAir Data, which issues its own ta_data_* keys from its own identically-named tool.

  ConnectorOAuth

• order-task-writeA

  WayfrontA

  Create, update, delete, complete or reopen order tasks. Every action requires order_number. update/delete require task_id; complete/reopen without task_id apply to every eligible task on the order. deadline is in HOURS. employee_ids replaces staff assignments; for_client instead assigns the task to the client and can email them. Omitted update fields stay unchanged. Moving sort_order below reached workflow tiers can reset assignments.

  Connector

  Destructive

  OAuth

• fenbs_add_decisionA

  fenbsA

  Record a decision, or ask a question for a person to decide. This is also how a RULE is recorded: a rule is a decision that holds from now on (standingRule true). When the person you work for says how something must always, or never, be done, record it here -- status decided, standingRule true, them in deciders, their words quoted in reason -- never as a context note. You may write a decision down; you never make one: record decided only when a person decided it. When nobody has decided yet, add it as open (the default) and ask. To change a rule, record a new decision with supersedes. Search fenbs_list_decisions first. Link the tasks that depend on it with tasks. Needs permission to change tasks.

  ConnectorOAuth

• lookA

  AstraNL CrossingA

  Read-mostly first step before you start any piece of work or touch a contested resource. Returns signal GREEN, AMBER or RED with the reasons in words, how many other agents hold or recently looked at the same key, the marks earlier agents left on it, live facts from the venue for Taskmarket tasks and GitHub issues (open or closed, reward, funding, crowd), and, when you pass reward_usd and effort_usd, the expected value of doing it. Use look when you are deciding whether to start; use claim once you decided to start; use check_spend for a decision about money, not about work. Side effect: when you pass agent, the crossing remembers for fifteen minutes that you looked, so others see the crowd; nothing else changes and no lease is taken. Safe to repeat.

  ConnectorNo auth

• fenbs_archive_completedA

  fenbsA

  Tidy the Completed lane in one call: archive every Completed task, or only those not changed for olderThanDays, of one project, or the refs given. Archived tasks leave the board but keep their refs and history, search still finds them, and fenbs_update_item archived false puts one back. Open work is never touched. Archive only when the person you work for asks; run with dryRun true first and tell them how many would go. Needs permission to move tasks.

  ConnectorOAuth

• list_my_issuesA

  BoardMarkA

  Open issues assigned to you in every project you can access, most recently updated first (D66 "My work"); on Sales & Billing projects also the unpaid installments of deals whose `owner` field is you (D130 (7)). With an agent account's token (D144): the issues assigned to the agent (`agt_…`), not to its owner. "What's on my plate?" — the issues assigned to you (the token's user) in EVERY project you can access, in one call, most recently updated first. Open issues only (not in a done-category status) unless `include_done: true`. Each item is an issue summary (`key`, `title`, `type`, `priority`, `status`, `assignee`, `points`, `sprint`, `version`, `updated_at`, …) plus `project_key` and `project_name`. Paginated with `cursor`/`next_cursor`. Use this instead of calling search_issues with `assignee=me` project by project; use search_issues when the user means one project or needs other filters. Call get_issue before changing any of these issues. Sales & Billing projects (D130): the installments (`type: subtask`, `parent` = the deal) of deals you own (`fields.owner`) are listed too, so an installment that is due or overdue on your deal shows here — read its `flags` (bill_due, due_soon, overdue).

  ConnectorOAuth

• search_linked_jiraA

  KaikuA

  Search a project's own Jira (see get_linked_jira_issue) with JQL, as its own search does — e.g. 'project = ACME AND status != Done ORDER BY updated DESC', 'text ~ "login"'; currentUser() is the project token's owner, not you. Answers each issue's jira_key, jira_url, summary, type, status, priority, assignee and when it changed; read one whole with get_linked_jira_issue. A query the site cannot read comes back with its reason. This is the other site's JQL; this tracker's own issues are searched with search_issues. Name the project by 'project', or an issue here by 'issue'. For the people who work in the project; at most 10 reads of the linked Jira a minute per person.

  ConnectorNo auth

• set_jira_connectionA

  KaikuA

  Switch a project's Jira connection on or off, keeping its token — and, with 'confluence', whether the same site's Confluence is read too. Off, nothing reads that Jira or writes to it — the issue screen, the agents, the status sync — and issues keep their keys there. Switched on, the held token is asked of the site first and refused with the site's reason if it no longer opens it. Connecting a Jira, or giving a new token — Confluence's own included — is done on the board's Jira sheet (get_jira_connection's 'url'), never here. For whoever administers the project.

  Connector

  Destructive

  No auth

• create_tasksA

  PlateA

  Create multiple tasks in a project in one action. Use this instead of calling create_task multiple times when the user asks to create several tasks at once. All tasks are created atomically — if validation fails for any item, nothing is created.

  ConnectorOAuth

• create_ganttA

  mcp-serverA

  Create a Gantt chart from a task list — no account or API key needed. YOU author the plan: list the tasks in execution order with realistic working-day durations and dependencies (0-based positions of earlier tasks; use { task, type, lag } for start-to-start/finish-to-finish links or lag). Milestones have duration 0. Only add a dependency where a task truly needs another one finished - independent tasks should run in PARALLEL (share a predecessor, or take no dependencies at all and start at the project start). Group tasks into top-level phases for a structured plan/WBS: the phase task gets isPhase: true, its tasks get parent = the position of the phase. LoopGantt schedules it with its critical-path engine and returns a picture of the chart, the dates, the critical path and a link where the user can view, export (PNG/PDF) and save the chart. Always show the user the link. Tasks with a due date take deadline: YYYY-MM-DD (a marker - the reply reports the fit). Use create_gantt when the user wants a chart to open, export or save; use schedule_project instead for what-if date math where nothing should be stored.

  ConnectorNo auth

• familia_create_list_taskA

  FamiliaA

  Use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items. If the same list task repeats across several days, weeks, or months, provide repeatRule and create one recurring list task instead of multiple one-time tasks. Do not use when editing an existing list attachment. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.

  Connector

  Destructive

  No auth

• familia_create_planA

  FamiliaA

  Use this when the user asks to create a Familia plan item for an event, trip, holiday, school, activity, care coverage, travel, chore block, or other scheduled family plan. If the same plan repeats across several days, weeks, or months, provide rrule and create one recurring plan instead of multiple one-time plans. If the user gives multiple dated or timed actions that clearly belong to the plan, such as flights, leaving for the airport, pickup, packing, check-in, or return travel, put the main event/trip in the plan and create each dated action as a relatedTasks entry instead of stuffing them all into notes. Do not use for standalone responsibility-style task reminders; use familia_create_task or familia_batch_write instead. Related tasks assigned to another household member can queue push notifications; schedules can trigger reminders, and delivered notifications cannot be recalled.

  Connector

  Destructive

  No auth

• bulk_create_tasksA

  WeftA

  Use this when the user wants to import many tasks at once — a CSV/JSON export from Linear, Jira, Notion or Trello, or any list of 3+ tasks from the conversation. Creates the whole batch in ONE call and one database transaction (all-or-nothing) instead of N create_task calls, so it is far cheaper on the monthly AI-call quota. Address columns by semantic ('backlog'/'todo'/'doing'/'done') or name; if the export references cycles/iterations, create the sprints first (create_sprint) and pass their sprintId per task. Tasks land in each column in array order, after the column's existing tasks.

  ConnectorOAuth

• get_issueA

  KaikuA

  Get one issue by key (e.g. 'UK-1') if it is visible to this token, including its description, status, assignee, labels, sub-tasks, the issues it is linked to and the wiki pages linked to it. 'comments' is a COUNT, not the text — read the thread itself with get_comments whenever it is not zero: decisions, the map of what is attached and how to run the thing are often written there rather than in the description.

  ConnectorNo auth

• propstack_create_taskA

  Propstack MCP by usefulapiA

  WRITE: create a note, a to-do (with due date) or an appointment (with start and end) in Propstack, linked to contacts, properties or projects. note_type_id is the activity type id (see propstack_get_reference_data activity_types). No e-mail or SMS is sent to the contact; the only mail is the reminder to the assignee when remind_at is set. Returns the new task id. POST /tasks.

  Connector

  Destructive

  No auth

• get_listing_signup_linkA

  Uganda Online Business DirectoryA

  Return the link for a Ugandan business owner to create a free listing in the Muyiribi directory. This tool does not create, edit, or verify any listing itself — the business owner completes signup and listing creation on the website. Use this whenever a business is not found in search results, or when a business owner asks how to get listed.

  ConnectorNo auth