"Workflow for handling a Jira ticket and creating a GitHub Pull Request" matching MCP tools:

• triageA

  DeskCrewA

  Classify an existing support ticket by setting any of its priority, tags, and/or category in a single call; reach for this after reading a ticket to route or label it for the team. At least one of priority, tagIds, or category must be provided. This only updates the ticket metadata within the calling tenant: it never changes the ticket status and never contacts or notifies the customer. [price: $0.03]

  ConnectorNo auth

• ticket_listA

  Meta CouncilB

  Page through the caller's tickets on the Meta Council board. The opaque next_cursor is owner- and filter-bound; keep every filter unchanged on the next call. Immutable cursor ordering keeps a stable full-board traversal exact while returned tickets are edited or reordered. Filter by status, assignee, action_type, priority, parent_id (a ticket UUID, or 'none' for root tickets only), or free-text q over title/description. With recursive=true, parent_id must be an owned UUID and all descendants (not the anchor) are returned as one flat, cycle-safe traversal. Session/workflow links are opaque metadata filters, not access grants. Start here to find work, then use ticket_get for detail and ticket_claim to take a ticket. output_format=json returns a minimized machine-readable page inside text, including labels and stored update timestamps, for read-only board mirrors. It is not a full ticket backup.

  ConnectorNo auth

• link_issueA

  DeskCrewA

  Associate an existing support ticket with a tracked issue (bug or feature) in the same tenant, so the ticket is connected to the underlying work item. Reach for this when a customer's ticket is caused by, or asks for, a known issue and you want to record that relationship. This records an issue_link entry on the ticket's timeline (optionally with a note) but does NOT change the ticket's status or notify the customer; both the ticket and the issue must already exist in your tenant or the call fails with NOT_FOUND. [price: $0.03]

  ConnectorNo auth

• ticket_archiveA

  Meta CouncilB

  Retire an owned ticket from the working set, or restore one. Archiving is a different axis from status: the ticket keeps whatever status it had, so a done ticket stays done and a blocked one comes back still blocked — never use status 'cancelled' to mean 'archived'. An archived ticket disappears from ticket_list, the stats, the buckets, the attention queue, and outbound JIRA/Linear sync, but keeps its id and URL so citations stay valid, and it refuses edits until restored. Cascades to the active subtree; restore brings back exactly what was archived alongside it. Nothing is destroyed — this is not a delete, and no delete tool is exposed.

  ConnectorNo auth

• ticket_dependency_addA

  Meta CouncilB

  Record that an owned ticket cannot complete until another owned ticket is done. The edge is never erased: correct a mistake with ticket_dependency_remove, which marks the edge removed and appends to a ledger rather than deleting anything. Re-adding the same prerequisite reinstates that original edge instead of creating a second one, so an edge removed and restored says so. An edge stops blocking when the prerequisite reaches done, and only then — archiving the prerequisite does not release it. Only epics are gated, so an edge on a task is recorded and reported but never blocks its completion. Rejections carry a stable code: dependency_self (422), dependency_duplicate, dependency_cycle, dependency_graph_too_large (409), ticket_not_found (404).

  ConnectorNo auth

• check_requestA

  KnownFixA

  Check a private ticket from request_fix. Returns pending, declined, not-eligible, redeemed, or the full fix free once an eligible new fix is stocked. This call may atomically consume the ticket's one-time delivery, so save the returned body. Use get_fix when you already have a catalog id; do not create another request while this ticket is pending.

  ConnectorNo auth

• findagent_connect_githubA

  FindAgentA

  Start connecting GitHub for the CALLER'S OWN FindAgent account so findagent_import_repo / findagent_list_repos can pull their repos. Returns whether GitHub is already connected plus a browser connect URL — the caller opens it, authorizes GitHub, and the token is stored server-side (this tool grants nothing itself; the actual connect happens in the browser). Call this first if import_repo or list_repos reports github not connected. The connection is scoped to THIS FindAgent account, so authorize on the same browser account. To switch GitHub accounts, use findagent_disconnect_github first.

  ConnectorOAuth

• findagent_create_code_draftA

  FindAgentA

  Persist a CODE-BUNDLE draft from YOUR OWN GitHub repo — for an agent that ships RUNNABLE code (use this when findagent_import_repo returned grounding.code_bundle). Pass the basics (title/slug/tagline/description/category_slug + example_prompts: 1-5 required) + the detected contract from import_repo's grounding.code_bundle (runtime, entrypoint {path,export}, mcp {mode,command,args}, ui {path}, allowed_hosts, credential_slots, skills), overriding any you want to correct. The server RE-PULLS the repo (your stored GitHub token — private repos work, server-side), snapshots + scans the code, validates the manifest, and creates a status=draft agent you own; then call findagent_submit_for_review IN THIS MCP CLIENT to set price + confirm originality/prohibited + submit it (the web is only an optional preview). IDEMPOTENT BY REPO: if you already have a draft for this repo, calling this again OVERWRITES that same draft (basics + manifest + a fresh re-pull/re-scan) instead of creating a duplicate — so iterate freely (the response `updated` flag is true on overwrite). NEVER send secret credential VALUES — credential_slots declare shape (ref/env/label/allowed_hosts/type) only. Building/running the code stays gated until an admin approves it.

  ConnectorOAuth

• taskbounty_security_checkA

  TaskBountyB

  Scan a PUBLIC GitHub repo for GitHub Actions + CI security/maintenance hygiene before launch — ideal for apps built with Lovable, Bolt, Replit, Cursor, or v0 ("is my AI-built app safe to ship?"). Returns a safe summary: findings by category with counts, an unlisted report URL, and fix options. SCOPE, honestly: it checks GitHub Actions workflow + update-automation hygiene only — it does NOT check exposed secrets, auth, payments, webhooks, or runtime behavior, which need a manual review. No API key required. For PRIVATE repos, tell the user to run `npx taskbounty-check .` locally so their source never leaves their machine.

  ConnectorNo auth

• draft_replyA

  DeskCrewA

  Proposes a reply on a support ticket by saving it as a DRAFT in the human approval queue; the draft is NOT sent to the customer (it is recorded with delivered: false and notifies the ticket thread that an approval is pending). Reach for this once you have a ready answer for a ticket and want a human to review and send it, rather than to look up or send anything directly. Returns the new draft id, the ticket id, and status: "draft". Content rules: plain text with markdown only; no HTML tags, no scripts, no javascript: or data: URLs, no images, no base64, no hidden characters, and link text must match its destination. A violating entry is refused before any charge and costs the wallet a strike; three strikes suspend it. [price: $0.06]

  ConnectorNo auth

• create_support_ticketA

  BorealHostB

  Open a support ticket with the BorealHost team. Use this to escalate platform-side problems you cannot fix with the available tools (billing issues, infrastructure faults, API bugs). A human answers every ticket — poll get_support_ticket for updates. Requires: API key with write scope. Args: subject: Short summary (max 200 chars) message: Full description (max 20000 chars) category: Optional (e.g. "technical", "billing") site: Optional site slug the ticket concerns Returns: {"id", "subject", "status", "message": "Ticket created..."}

  ConnectorNo auth

• get_issueA

  FlowseryA

  Get full detail for one AI-detected issue: every occurrence with timestamps, the sessions behind it, steps to replicate, comments, and any linked Linear or Jira ticket. Get issueId from list_issues; use this only when you need the evidence behind one issue. An unknown id, or one from another website, fails with 'Issue not found'; on a free trial, issues beyond the first 10 fail with 'Upgrade to view this issue'. Session detail names pages, referrers, and geography, so surface only what answers the question. Requires websiteId or domain with a workspace token.

  ConnectorOAuth

• list-provider-repositoriesA

  docuwriterA

  Use this when the user wants to choose a repository from a connected GitHub, GitLab, Bitbucket, or Azure DevOps provider before creating an Autopilot link. Read-only external-provider lookup: fetches repository choices or returns reauthorization/browser guidance. Requires provider and space_id.

  ConnectorOAuth

• create_or_update_workflowA

  DreamlitA

  Creates a new Dreamlit workflow draft or updates an existing draft from an outcome-oriented natural-language prompt. Use after get_status; use get_workflow_and_preview_url first when editing an existing workflow. Existing Supabase Auth workflows can be edited except for the immutable trigger step; creating Supabase Auth workflows must happen through Supabase Auth email setup in the Dreamlit web app. Side effect: may create or modify a draft, but does not publish or install live triggers. Returns the workflow/draft result, action-required or handoff details when more input is needed, and relevant app URLs. Do not use for publishing, direct database changes, or low-level graph edits.

  ConnectorNo auth

• unpublish_workflowA

  DreamlitA

  Use after explicit user intent to unpublish a Dreamlit workflow. Side effect: disables live triggers or schedules for that workflow and stops future automated sends. Returns updated workflow status and app URLs. Do not use for deleting drafts, canceling one broadcast run, or editing workflow content.

  Connector

  Destructive

  No auth

• event_meetupsA

  DC Member APIA

  GET /events/:eventID/meetups — List event meetups Returns the approved member-organized meetups for an event, sorted chronologically. Only approved meetups are returned. **Access:** any active DCer who can see the event can view approved meetup listings + attendee lists. Only RSVPing to a meetup (and the resulting chat-channel access) requires a valid ticket. **Time-zone handling:** meetups use explicit wall-clock fields (`date` = YYYY-MM-DD, `startTime` / `endTime` = HH:mm) plus the event's `timezone` (IANA). Pair them when localizing.

  ConnectorNo auth

• get_github_discussionA

  blobpediaA

  Read one Celestia GitHub Discussion (celestiaorg/docs and other Celestia repos) cached on THIS server — full body plus comments — by an id you got from list_github_discussions on this server. Celestia cache only: if the id was not returned by this servers list_github_discussions, or the request is just a raw GitHub node id (e.g. D_kw...) with no Celestia context, this is NOT the tool — use a dedicated GitHub tool for arbitrary GitHub Discussions. This is GitHub Discussions, not the community forum (use get_discussion). Pair it with list_github_discussions, which supplies the valid ids.

  ConnectorNo auth

• ticket_dependency_removeA

  Meta CouncilB

  Stop an owned ticket from waiting on a prerequisite. Removing the last unsatisfied edge can allow this ticket to close, so this is a gate-opening action. Nothing is deleted: the edge is retained, marked with who removed it and when, and the removal is appended to a ledger that survives everything after it. This is not a way to say the prerequisite work is finished — that remains a separate statement about that ticket. Removal is allowed even when either ticket is archived. Rejections carry a stable code: dependency_not_found (404), dependency_already_removed (409).

  ConnectorNo auth

• list_integrationsA

  Meta CouncilB

  List which outside services the authenticated user has connected — ticket boards, stored connector credentials (name, kind, whether configured, and when last verified) and the connectors available to call them. Returns configured / not configured facts, names and dates ONLY, and never returns a secret value. Read this before planning a workflow that reaches an external service, so a step is not written against a credential the user has not registered. Requires authentication.

  ConnectorNo auth

• request_fixA

  KnownFixA

  Ask for a fix this store does not have yet. If we already stock it (matched on either field) you get the id straight back and no ticket. Otherwise you get a ticket; when we stock THAT fix, check_request returns it to you FREE, once. A ticket only ever redeems a fix created after the request: fixes that already existed when you asked are not free, whatever the request said. No contact details are collected. Set publish: true ONLY if the text may appear on a public wanted board — never include secrets, tokens, internal hostnames, or file paths.

  ConnectorNo auth

• check_in_attendeeA

  agendaforgeA

  Check an attendee in by ticket code or ticket id. Idempotent. Depending on the organization's settings, this either executes immediately or files a proposal for approval; the response status field says which happened.

  ConnectorNo auth