"Automating Jira or Trello ticket creation using MCP" matching MCP tools:

• triageA

  DeskCrew - AI Chatbot, Helpdesk & Knowledge baseA

  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

• link_issueA

  DeskCrew - AI Chatbot, Helpdesk & Knowledge baseA

  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

• engage_sasameA

  SaSame MCP Observatory + Gold Rush TownB

  Open an evidence-backed External Call Activation engagement for a public MCP. Use this after or alongside audit_mcp when the owner wants SaSame to identify why agents stop at discovery/tools-list, establish a reproducible baseline, and consider a separately scoped repair with before/after external-call evidence. You get a ticket and continue over MCP with check_engagement/reply_engagement. Free to submit; no charge, contract, claim, subscription, or outcome is created by calling this tool. Do not paste secrets, credentials, or private payloads.

  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

• export_ticket_to_providerA

  Meta CouncilB

  Export the exact previewed owned ticket to Jira or Linear, using expected_export_hash from preview_ticket_export and the same destination. Requires explicit integrations:write, tickets:write, and independent human approval of the complete preview. Persists the operation before possible remote writes. After an uncertain response, inspect list_ticket_provider_effects and reconcile the original intent; never blindly export again. Remote confirmation is observed, not atomic protection against concurrent remote writers.

  ConnectorNo auth

• get_image_upload_ticketA

  OnlyWorldsA

  Get a ticket to upload ONE image into this world, for an element's `image_url` (Keel #59). The image never passes through this tool: you send its bytes yourself, straight to the image host, with the ticket. Steps: 1. Call this tool. You get `ticket`, `upload_url`, `max_bytes` and `exp`. 2. Upload the image yourself: `curl -X POST <upload_url> -H "Authorization: Bearer <ticket>" --data-binary @picture.webp` (raw bytes as the body; webp, png, jpeg or avif, no SVG; at most `max_bytes`; before `exp`). The host answers 201 with `{url, key, bytes, type, etag}`. 3. Set the element's picture: `update_element(type, id, {"image_url": <url>})`. One ticket, one upload: a second upload with the same ticket is refused (401 ticket_used); call this tool again for the next image. Each ticket counts toward the world's daily limit, and each upload toward its account's image storage (1 GB by default; `max_bytes` shrinks to what is left, and a full account is refused). Requires a WRITE API-Key and its PIN.

  ConnectorNo auth

• account_api_key_statusA

  SAVORDISHA

  Check the status of the API key you're using right now — see call count, rate limit, and creation date. Useful for monitoring your MCP usage. TRIGGERS: - 'check my API key', 'API key status', 'how many calls have I made' - 'my usage', 'rate limit status', 'key info'

  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

• aimrank_list_public_judgesA

  AimRankA

  Browse public judge-prompt artifacts shared by other users. Filter by ``category`` (free-text), ``domain_id``, or both. Sort options: ``fork_count`` (default — most-forked first), ``recent``, ``faithfulness``. Returns artifact summaries WITHOUT the full prompt text — call `aimrank_fork_judge_prompt` or the REST GET to retrieve the full prompt before using it. api_key is optional on the public endpoint; on /mcp/mcp a missing key is refused.

  ConnectorNo auth

• get_testA

  UxiaA

  Read metadata for one accessible test using testId from list_tests: title, goal, status, type, source, creation date, version, result flag and Uxia link. Does not return findings, screenshots or session data; use result tools for those.

  ConnectorOAuth

• propose_resolutionA

  DeskCrew - AI Chatbot, Helpdesk & Knowledge baseA

  Submit a proposed resolution for an existing support ticket as a DRAFT for human approval: it is queued for a human agent to review and is NOT sent to the customer and does NOT close the ticket. Reach for this once you have diagnosed a ticket and have a concrete, customer-ready answer or fix to suggest. The ticket is looked up by id within the authenticated tenant; if no matching ticket exists the call is refused. 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

• prepare_provider_actionA

  Not Human SearchA

  Prepare a signed action ticket for a separately disclosed provider-funded offer returned beside a receipt-bearing NHS discovery result. This step never returns the provider action URL or records a handoff. It requires the discovery receipt and the caller's explicit ticket-authorization attestation. It accepts controlled constraints only—no name, email, contact detail, raw prompt, agent identity, or principal identity fields. Discovery and direct provider access remain free; preparing a ticket charges neither party. Exact v1 wording: https://nothumansearch.ai/privacy#consent-v1

  ConnectorNo auth

• reply_to_support_ticketA

  financeA

  Reply to one of the user's own support tickets. If the ticket was resolved or closed, replying reopens it (the service layer handles this), so the user can resume the conversation. Writes to Zoninga's own support desk (no third-party service). API docs: https://zoninga.com/ai/#support-tickets Args: ticket_id: The ID of the ticket to reply to. body: The reply text (1-5000 chars). Returns: ``{"success": True, "reply": {...}, "ticket": {"id", "status"}}`` (``ticket.status`` reflects any reopen), or ``{"error": "..."}`` if the ticket isn't found / isn't the caller's, or the body is invalid.

  ConnectorAPI key

• preview_ticket_exportA

  Meta CouncilB

  Preview the exact owned ticket content, destination, correlation marker and status mapping for Jira or Linear. Supply destination (Jira project key or Linear team key) for an unlinked ticket. Returns expected export hash; no provider request or external write. Requires explicit integrations:write and tickets:write. Review this preview before export; a changed ticket or provider credential needs a fresh preview.

  ConnectorNo auth

• create_participantsA

  User IntuitionA

  Queue creation of 1–100 unique BYOP participants. Poll get_participant_job until succeeded, then list participants. Before creating participants, call get_study, require provisioning_status=provisioned, and verify or obtain explicit approval of the current plan. Carry a trusted unchanged approval forward using study_id and updated_at; changed plan or invitation settings invalidate it. Invitations send unless silent is true.

  ConnectorOAuth

• prepare_media_uploadA

  550W Watermark & Text EraserA

  Get a short-lived upload ticket. POST multipart to uploadUrl with X-550W-Upload-Ticket; no OAuth token is needed on that upload. Uploading an image starts a paid image-erasure task: use the returned taskId with get_image_watermark_task until terminal status; there is no separate image creation tool. Video upload only prepares media; then call submit_subtitle_task. Obtain user consent for upload and paid processing first. Image uploads require an 8–64 character operationId and the same file on retry. Failed, deleted or expired operations are not recreated.

  ConnectorOAuth

• compass_changes_upsertA

  ZeroWidth CompassA

  Create or update up to 100 changes in one call, each matched by `url` — the GitHub issue, Linear or Jira ticket, PR or doc it mirrors. A url already linked to a change updates that change (label, description, status, tags, experiment, workflow — omitted fields are left alone); any other url creates a change with that link. Run it again with the same urls to keep Compass in step; nothing duplicates. Statuses are by name (compass_statuses_list). Returns one result per item — created / updated with the change's key, or failed with why; a failed item doesn't stop the rest. Summarize what you're about to bring in before calling. May return `needs_confirmation` — one approval covers the whole batch.

  Connector

  Destructive

  No auth

• compass_changes_upsertA

  ZeroWidthA

  Create or update up to 100 changes in one call, each matched by `url` — the GitHub issue, Linear or Jira ticket, PR or doc it mirrors. A url already linked to a change updates that change (label, description, status, tags, experiment, workflow — omitted fields are left alone); any other url creates a change with that link. Run it again with the same urls to keep Compass in step; nothing duplicates. Statuses are by name (compass_statuses_list). Returns one result per item — created / updated with the change's key, or failed with why; a failed item doesn't stop the rest. Summarize what you're about to bring in before calling. May return `needs_confirmation` — one approval covers the whole batch.

  Connector

  Destructive

  No auth

• setup_instructionsA

  Coal — Payments for AI agentsA

  Print step-by-step instructions for using Coal MCP from Claude / Cursor / any MCP client. Run this FIRST if you are unsure how to authenticate or which credentials to provide.

  ConnectorNo auth

• jira_to_test_suiteA

  IA-QA — 130+ QA & Dev Tools for AI AgentsB

  Transform a Jira ticket into a complete test suite: Gherkin scenarios, E2E steps, API test cases, test data matrix, and ambiguity detection. Accepts either Jira credentials (auto-fetch) or a pre-fetched issue object. The returned test_suite includes _gherkin_warnings (deterministic syntax validation — empty if clean). Requires BYOK LLM key (OpenAI, Anthropic, etc.).

  ConnectorNo auth

• recompute_deadlinesA

  transaction-coordinatorA

  Re-run FRCP / state procedural deadline calculation for a matter. Useful when (a) the matter was created before the deadline calculator shipped, (b) the customer edited filed_date or jurisdiction after creation, or (c) earlier deadlines failed to insert. Idempotent — dedupes on lowercased title so re-running can't duplicate. Args: matter_uuid: UUID of the matter to recompute. api_key: Your PrimaCoda MCP API key (starts 'pck_').

  ConnectorNo auth