Skip to main content
Glama
682,948 tools. Updated 2026-10-21 02:21

"Using an MCP server with Atlassian JIRA to extract ticket descriptions" matching MCP tools:

  • 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
  • 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
  • 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 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
  • PAID ($0.01). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.
    ConnectorNo auth
  • 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

Matching MCP Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    UK property listing description generator. Give an AI assistant a postcode or address — it fetches comparable sales, EPC ratings, and Rightmove listings, then writes three copy variants ready for Rightmove, social media, and email.
    1
    -

Matching MCP Connectors

  • 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 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 only the first 10 issues are available, and later ones fail as not included in the current plan. Each session lists its recording id, the anonymous visitorUid, start URL and page title, timing and event counts; no names, emails or locations are returned, so surface only what answers the question. Requires websiteId or domain with a workspace token.
    ConnectorOAuth
  • ANSWER ON YOUR TICKET — and, when it is `pending`, CLOSE IT OR SEND IT BACK. `verdict: "fixed"` means you ran the `verify` line from gap_check and it works: the ticket closes stamped as confirmed by the reporter. `verdict: "still_broken"` means you ran it and it does not: the ticket goes straight back onto the queue, red, with your sentence as the reason it bounced — no re-filing, and that line is the most useful one on the whole list, because it says a fix we believed in did not hold. A verdict only applies to a `pending` ticket: nothing else is waiting on your answer, and on an open or closed one your message lands in the thread for a person to read instead. Leave `verdict` off to just add to the ticket. `still_broken` needs the sentence — say WHAT is still wrong, or it goes back to a queue with nothing to act on. Same rule as filing: describe the capability, never the person, and never paste your human's brief.
    ConnectorNo auth
  • 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
  • Buy the ticket for a flight from search_flights, paid in USDC. Call it first without payment to get the price, wallet address and MPP challenges. After sending the USDC, call it again with tx_hash and chain (or an MPP credential in _meta "org.paymentauth/credential"). x402 clients can instead sign one of the offers in error.data.x402 and retry with the PaymentPayload in _meta "x402/payment", with no gas needed. Returns the ticket link and PDF.
    ConnectorNo auth
  • 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
  • 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
  • PAID ($0.01). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.
    ConnectorNo auth
  • PAID ($0.01). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.
    ConnectorNo auth
  • Get a support ticket with its full message thread. Requires: API key with read scope. Args: ticket_id: Ticket UUID from list_support_tickets Returns: {"id", "subject", "status", "messages": [...]}
    ConnectorNo auth
  • 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
  • Add a message to an existing support ticket of the account, optionally with images (screenshots): PNG, JPEG, WEBP or GIF in base64, at most 5 per message; the whole MCP request is limited to 1 MB (so about 700 KB of images). The text may be empty when an image is attached. Returns the id of the new message and the updated ticket. (permission: support:write) [Requires a free GPU Cloud account and MCP key]
    ConnectorNo auth
  • 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
    Destructive
    No auth
  • 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
  • Assigns an existing ticket to a human agent on this tenant, recording an assignment event on the ticket timeline. Reach for this to route or hand off a ticket to a specific teammate. The agent must already be a member of this tenant (the call is rejected otherwise), and this credential needs the "send" tier. [$0.06 draft / live when trusted]
    ConnectorNo auth