"Managing and searching Jira ticket creation" matching MCP tools:

• resolve

  DeskCrew

  Marks a ticket as resolved by setting its status to "closed" and recording an internal status-change note on the timeline. Reach for this once the issue has been handled and you want to close it out; it is idempotent (a no-op returning changed:false if the ticket is already closed) and reversible (a human can reopen it from the dashboard). Requires the "send" tier on this credential. The note is an internal audit entry only and is NOT delivered to the customer. [$0.06 draft / live when trusted]

  Connector

• delete_ticket

  Sweeppea MCP

  Permanently delete an open support ticket. Use fetch_open_tickets first to get the case_id. WARNING: This action cannot be undone. Only open tickets can be deleted. # delete_ticket ## When to use Permanently delete an open support ticket. Use fetch_open_tickets first to get the case_id. WARNING: This action cannot be undone. Only open tickets can be deleted. ## Parameters to validate before calling - case_id (string, required) — The case number of the ticket to delete ## Notes - DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.

  Connector

• send_reply

  DeskCrew

  Sends a reply to the customer on an existing ticket and DELIVERS it immediately (customer email plus any connected chat threads) — this is not a draft and reaches the customer. Use this once you have a final, customer-ready answer; to instead queue a reply for human approval, use the draft tool. Requires a "send"-tier credential (a draft-tier credential is refused) and the ticket must already have a customer email on file or the call is rejected. [$0.06 draft / live when trusted]

  Connector

• list_tickets

  DeskCrew

  Read-only: list support tickets in the caller's tenant, sorted by most recent message first. Reach for this to discover ticket ids, triage the queue, or poll for activity before acting on a specific ticket; results can be narrowed by status, priority, assignee, and an updated-since timestamp, and capped via limit (max 50, default 20). Returns lightweight ticket summaries (id, subject, status, priority, lastMessageAt, customer, assignee, tenant) plus the total match count — it never creates or modifies anything. [free]

  Connector

• link_issue

  DeskCrew

  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]

  Connector

• discover_collections

  Ragora

  Discover all knowledge bases you have access to. Returns collection names, descriptions, content types, stats, available operations, and usage examples for each collection. Call this first to understand what data is available before searching.

  Connector

• list_categories

  opendata-cat

  List all dataset categories and themes with counts per portal. Great first step to discover what data types are available before searching with search_datasets. Returns total datasets, count per portal and category list with counts. No parameters required.

  Connector

• usaspending_search_federal_accounts

  usaspending-mcp-server

  List and keyword-search federal accounts by agency identifier or title keyword. Returns account numbers, names, managing agencies, and budgetary resources. Use account_number from results as input to usaspending_get_federal_account for full budget detail. Use usaspending_list_agencies to look up agency_identifier codes (3-digit strings, e.g. "097" for DoD).

  Connector

• list_health_topics

  Myhealthfinder

  Browse the ODPHP/health.gov catalog — list all health topics or all categories (Cancer, Diabetes, Heart Health, Screening Tests, …). Use to discover what guidance exists before searching.

  Connector

• list_filters

  Jobs Base

  Get available filter values for search_jobs: job types, workplace types, cities, countries, seniority levels, and companies. Call this first to discover valid filter values before searching, especially for country codes and available cities.

  Connector

• get-conference-info

  elc-conference-mcp-tickets

  Get details about the ELC Conference 2026 — date, venue, speakers, topics, what's included, and ticket link. Use this when someone asks about the conference.

  Connector

• list_filters

  Jobs Base

  Get available filter values for search_jobs: job types, workplace types, cities, countries, seniority levels, and companies. Call this first to discover valid filter values before searching, especially for country codes and available cities.

  Connector

• file_support_ticket

  Vocab Voyage

  File a real human-followup support ticket on behalf of the signed-in user. Use this when the user reports a billing problem, bug, account lockout, complaint about a tutor, or anything Sparkle/the agent cannot resolve from data. The ticket is emailed to the support team and a confirmation is sent to the user with a 1-business-day SLA. Categories: billing, bug, account, complaint, feedback, other. Requires sign-in.

  Connector

• engage_sasame

  SaSame MCP Observatory + Gold Rush Town

  Commission SaSame to BUILD or OPERATE an AI system. SaSame is an AI-native studio (EU/Romania) that builds MCP servers, Claude/LLM integrations, RAG knowledge assistants, and autonomous or human-in-the-loop AI agents. Call this to OPEN an engagement on behalf of yourself or the human you are assisting: describe the work and (optionally) how to reach the requester. You get back a `ticket`. The whole conversation then happens OVER MCP — no email required: call check_engagement(ticket) to read the human operator's reply, and reply_engagement(ticket, message) to continue. Free to submit. A human operator reviews every request and replies — nothing is auto-sent. Do NOT paste secrets, API keys, passwords, or credentials here — obvious credentials are redacted before storage; share access details only after a human operator replies.

  Connector

• list_tickets

  Muninx MCP Server

  List tickets visible to the Muninx API token owner within the authenticated tenant. Behavior depends on the token owner's role: customers cannot filter by creator or assignee; agents cannot filter by assignee and, unless participant is supplied, see tickets assigned to themselves; admins can use all filters. Do not combine creator and participant. For MCP input, state and priority must be arrays of enum values, not comma-separated strings. Use ticket titles and metadata for user-facing summaries; ticket IDs are mainly for follow-up tool calls.

  Connector

• propose_resolution

  DeskCrew

  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. [price: $0.06]

  Connector

• delete_request

  Ssemble AI Clipping

  Permanently delete a short creation request and all generated videos. Credits are NOT refunded. This action is irreversible.

  Connector

• list_categories

  Not Human Search

  List all categories in the Not Human Search index with site counts and average agentic scores. Use this to understand what kinds of agent-ready services exist before searching — counts are live, so the distribution shifts as the index grows.

  Connector

• freshdesk_search_tickets

  Freshdesk

  Search tickets by query (e.g., "status:2 AND priority:3" or keyword text). Returns matching ticket ID, subject, status, and priority.

  Connector

• virtualsms_get_profile

  sms

  Full account profile: email, Telegram link status, current balance, lifetime spend, total orders, active API keys, and account creation date.

  Connector