Search Jira using JQL (Jira Query Language). Returns matching issues with key fields. Ideal for finding open bugs, sprint tickets, or issues by label/assignee/component. BYOK — credentials transit in-memory only, never stored.
Connector
213,473 tools. Last updated 2026-06-19 17:07
"Finding JIRA MCP to Create and Edit Jira Tickets" matching MCP tools:
- Create billable async Cannon Studio generation work only after explicit user approval. Requires OAuth or a developer API key; can spend credits up to max_credits and cannot be cancelled through MCP after submission. Use estimate_generation_cost first, then set confirmed=true and a user-approved max_credits cap. This tool does not create API keys, charge payment methods directly, or delete assets.Connector
- Publish a pending edit after the user has approved the preview. ONLY call after suggest_edit, user saw the preview, and explicitly approved.Connector
- 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.Connector
- Discover today's best deals ranked 0–100 — answer "what are the best deals right now?" without a specific product, ACROSS EVERY VERTICAL. `surface` selects the inventory: shopping (default — retail deals by stored deal score), hotels (biggest 7-day nightly-rate drops), events (activity rate drops), tickets (live-event tickets priced below their 30-day median, with a reasons[] breakdown), or all (one response grouped into labeled per-surface sections — hotels, things to do, event tickets, shopping). Rows carry a drillDownTool for the next call (hotel_details / activity_details / ticket_details / price_check). Optional `category` filter (shopping only) and `minDealScore` (shopping defaults to 60; other surfaces filter only when provided). URLs are pricetik.com/go/ affiliate redirects — pass them to the user's browser unchanged, do not fetch them server-side. No API key required. For a specific query use pricetik_search; for deals ranked to the user's stated interests use pricetik_deals_for_you.Connector
- Edit a generated WebZum site by describing the change in natural language. This is the primary editor tool. Given a user instruction (in conversationHistory), the WebZum editor builds the minimal site tree, sends it to an LLM with the user's verbatim words, applies the returned HTML diff across every page that contains each affected section, and reassembles into a new version. Use this for nearly all edits: "make the hero say X", "remove the testimonials section", "change the about-us copy to be friendlier", "swap the order of the sections on the home page". Required: businessId, versionId, and a conversationHistory containing at least one user turn. The LLM reads the user's verbatim words — do not paraphrase. Returns { versionId, status: 'completed' | 'in_progress', ...extra }. If status is 'in_progress', the edit is still running in the background — poll get_site_status with the returned versionId every 5-10s until isComplete is true. Concurrency: edits on the same businessId MUST be serial. Never fire parallel edit calls on the same site; concurrent edits race and may return the wrong versionId. Wait for each edit to complete (status: 'completed' OR isComplete on get_site_status) before issuing the next one.Connector
Matching MCP Servers
- AlicenseAquality-maintenanceEnables AI assistants to interact with Atlassian Jira Cloud, allowing users to manage projects, issues, comments, and workflows through natural language commands.Last updated61033
- AlicenseAquality-maintenanceA Model Context Protocol (MCP) server for interacting with Atlassian Jira. Connect AI assistants like Claude, Cursor AI, and others directly to your Jira projects, issues, and workflows.Last updated61033
Matching MCP Connectors
Jira MCP Pack
Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.
- Replace the text of an existing message in a Telegram chat. Only works on messages sent by the authenticated account. Cannot edit media or other message attributes — text only. Success: dict with message_id, date, chat, text, status='edited', and edit_date. Error: dict with ok=false and error string (e.g. message not found or not editable). Use edit_message to update a previously sent message; use send_message to create new ones. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.mdConnector
- Persist a generated workflow (name, description, body, outcome, tags). Addressing: omit ``workflow_id`` to save in your own namespace, which updates your own workflow of this name or creates a new one. Saving by name never edits a workflow someone else shared with you. To edit a workflow you own or have edit access to, pass its ``workflow_id`` (and a matching ``name``). If a workflow of this name is shared with you at edit access and you save by name alone, the reference is ambiguous and the call asks you to address it by id. Optional ``source`` ('manual' | 'teach' | 'optimization' | 'description_optimization' | 'audit') attributes the version to a manual save, a teach_workflow session, a workflow optimization session, a description optimization session, or an audit_workflow session; omit to leave NULL. Returns workflow_id and version. Workflows are private to the caller; share via publish_template_version.Connector
- DEPLOY THE CURRENT MAIN BRANCH TO A-TEAM CORE. ⚠️ HEAVIEST OPERATION (60-180s): validates solution+skills → deploys all connectors+skills to Core (regenerates MCP servers) → health-checks → optionally runs a warm test → auto-pushes to GitHub. 🌳 DEV/PROD WORKFLOW: 1. Edit files → ateam_github_patch (writes to `dev` branch by default) 2. (Optional) Preview what's about to ship → ateam_github_diff 3. Ship dev → main → ateam_github_promote (merges + auto-tags `prod-YYYY-MM-DD-NNN`) 4. Deploy main to Core → ateam_build_and_run This tool ALWAYS deploys the `main` branch — there is no `ref` parameter. To deploy in-progress dev work, first promote it. AUTO-DETECTS GitHub repo: if you omit mcp_store and a repo exists, connector code is pulled from main automatically. First deploy requires mcp_store. After that, edit via ateam_github_patch + promote, then build_and_run. For small changes prefer ateam_patch (faster, incremental). Requires authentication.Connector
- Configure automatic top-up when balance drops below a threshold. The configuration lives ONLY in the current MCP session — it is held in memory by the MCP server process and is lost on server restart, MCP client reconnect, or server redeploy. Top-ups are signed locally with TRON_PRIVATE_KEY and sent to your Merx deposit address (memo-routed). For persistent auto-deposit you currently need to call this tool again at the start of each session.Connector
- Return a live inventory of all active endpoints and MCP tools. Use this first to discover what the API can do before making calls. Returns tool count, endpoint list, MCP-exposed tools, and usage notes. Deterministic -- no LLM cost.Connector
- Start a shared GROUP trip-planning session that friends join by share code — the multi-user counterpart to pricetik_trip_plan. Pass destination (plus optional checkIn/checkOut/title). Returns the session, a shareCode, and a shareUrl (pricetik.com/trips/<code>) — give BOTH to the user so companions can join from their own agent (pricetik_group_trip_join) or vote on the web page without one. Choreography: create → search hotels/activities/tickets as usual → pricetik_group_trip_add_option for the strongest candidates → members vote → organizer finalizes. The creator becomes the session organizer. Requires an authenticated API key; pass an Idempotency-Key header to make retries safe. Sessions are coordinate-only — booking stays per-traveler via the booking-url tools; PriceTik never books on anyone's behalf.Connector
- 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
- Update fields of a single verse in a collection (restricted: requires X-MCP-Write-Token; owner-scoped). Only the fields you pass are changed. For the nullable fields `source`/`topic`/ `image`, pass an empty string to clear them; `reference` and `passage` cannot be emptied. You can only edit verses owned by the configured write owner. Args: verse_id: The verse ID (from get_collection_detail). reference: New reference (e.g. "John 3:16"). passage: New verse text. source: New translation/source code ('' clears it). topic: New topic label ('' clears it). image: New image URL ('' clears it).Connector
- Long-poll: blocks until the next edit lands on this board, then returns. WHEN TO CALL THIS: if your MCP client does NOT surface `notifications/resources/updated` events from `resources/subscribe` back to the model (most chat clients do not — they receive the SSE event but don't inject it into your context), this tool is how you 'wait for the human' inside a single turn. Typical flow: you draw / write what you were asked to, then instead of ending your turn you call `wait_for_update(board_id)`. When the human adds, moves, or erases something, the call returns and you refresh with `get_preview` / `get_board` and continue the collaboration. Great for turn-based interactions (games like tic-tac-toe, brainstorming where you respond to each sticky the user drops, sketch-and-feedback loops, etc.). If your client DOES deliver resource notifications natively, prefer `resources/subscribe` — it's cheaper and has no timeout ceiling. BEHAVIOUR: resolves ~3 s after the edit burst settles (same debounce as the push notifications — this is intentional so drags and long strokes collapse into one wake-up). Returns `{ updated: true, timedOut: false }` on a real edit, or `{ updated: false, timedOut: true }` if nothing happened within `timeout_ms`. On timeout, just call it again to keep waiting; chaining calls is cheap. `timeout_ms` is clamped to [1000, 55000]; default 25000 (leaves headroom under typical 60 s proxy timeouts).Connector
- Run a natural-language analytics question against your connected data sources. Consumes AI credits. Returns either the completed analysis result inline OR a job_id you can poll with get_analysis_status. If list_data_sources returns an empty list, ingest data first with upload_data_source (inline base64), ingest_url_data_source (public URL), or request_oauth_integration_url (Google / Meta / Jira / Confluence).Connector
- Return a live inventory of all active endpoints and MCP tools. Use this first to discover what the API can do before making calls. Returns tool count, endpoint list, MCP-exposed tools, and usage notes. Deterministic -- no LLM cost.Connector
- Find MCP servers in the directory. Searches the standalone MCP directory (PulseMCP / official MCP registry import) unioned with x402 services that also expose an MCP endpoint. Returns normalised entries with a ready-to-use streamable-http `call_hint.mcp.url`. Args: intent: Natural-language description of the tool/capability needed. top_k: Max servers to return (1-20). chain: Optional payment-network filter for paid MCP servers. require_healthy: When true, only return servers marked health=ok.Connector
- Initiate an OAuth handoff to a vendor integration (Google Ads, GA4, Search Console, Sheets, Drive, BigQuery, Meta Ads, Jira, Confluence). Returns an authorization URL the user opens in a browser. After the user clicks Allow, the connection is created and you can poll check_integration_status(handoff_id) to find out when the data is ready.Connector
- Single-call orchestrated trip planner — stitches top hotels + recommended activities + estimated spend into one response, so the agent skips the manual "search hotels → search activities → stitch" fan-out. Pass destination + dates (plus optional budget, interests, star rating, no-resort-fees). For a HOTEL + SHOW/CONCERT/GAME trip, set includeTickets=true (plus ticketQuery for a specific performer, team, or show) — the plan then carries an eventTickets[] block of live-event tickets matched to the destination and stay window. Tickets are affiliate inventory: each carries a checkout link the user opens on the ticket seller, and ticket prices are NOT included in estimatedTotalUsd. Set groupByDay=true for a daily itinerary with rest-day placeholders on trips longer than 5 nights and 4h+ activity conflict avoidance. Pass includeTransfer to attach the best-value ground transfer (airport / port / station ↔ hotel) to the plan — it carries a rateToken you can hand to pricetik_transfer_get_booking_url; an uncovered or same-type terminal route returns a non-fatal transferUnavailable note and the hotel + activity plan still comes back. Free at every tier. Stricter rate limit than single-surface tools (10/min) because it fans out parallel searches. Direct REST callers can append ?stream=ndjson (or send Accept: application/x-ndjson) for incremental frames. Use this for a single-call hotel + activity (+ event ticket) stitch; for hotels only, use pricetik_hotel_search; for tickets only, use pricetik_ticket_search.Connector