"How to view or read a Jira ticket" matching MCP tools:

• 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_esims

  PikaSim

  List every eSIM this wallet owns (the fleet view), newest first: ICCID, plan, order status, install link, and — for fleets of up to 8 — live remaining data inline. Read-only. Use this to answer "which eSIMs do I own / how much data is left" without already knowing an ICCID; then get_esim_status for any single eSIM's full detail. eSIMs only — SMS numbers are listed by list_sms_orders. Requires a connected agent wallet.

  Connector

• sequencing_readback_verify

  workbench

  Align raw Sanger or NGS reads (FASTA or FASTQ) back onto a claimed reference sequence using minimap2, and report per-read mapping identity plus exact variant positions (substitutions/insertions/deletions), with a consensus view across reads and a corrected consensus sequence (the reference with every consensus-supported edit applied). Complements verify_construct/verify_assembly: those re-derive what a design SHOULD produce from its own stated inputs; this checks what a real sequencer actually read back.

  Connector

• list_repos

  blobpedia

  List the GitHub repositories that blobpedia has INDEXED for Celestia, with item counts. Read-only view of the Celestia index on this server — does NOT browse your GitHub account or arbitrary repos (use a dedicated GitHub tool for that). Zero arguments.

  Connector

• manage_account

  Bassethound

  See your plan and get a link to manage, switch, or cancel your paid Bassethound subscription. Call this when the user wants to cancel, update their payment method, view invoices, move between Pro and Business, or check which plan they're on. A paid user gets a Stripe Customer Portal link — Stripe hosts all billing management, and cancelling there keeps the plan active until the end of the billing period; a free user is told how to upgrade.

  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

• scan_ai_visibility

  TofuBofu AI Visibility

  Start a free AI-visibility scan for a B2B company's website. Checks how often AI engines (ChatGPT, Claude, Perplexity, Gemini) name the company when buyers ask for vendor recommendations, and finds the gaps. The scan runs in the background (roughly 1-2 minutes); call get_visibility_report with the returned report_id to read the score and findings. Args: domain: The company's website or domain, e.g. "acme.com". email: The user's work email. Required, we send the finished report here and it identifies the account. One free scan per email per month. Returns: report_id, a report_url to view live, and whether an existing report was reused (free scan already used this month).

  Connector

• create_support_ticket

  Dock

  File a support ticket. Mirrors to a GitHub issue in Dock's support repo and shows up in the user's dashboard at /settings/support. Use this for bugs (you hit an error), feature requests (Dock is missing something), billing (Stripe/subscription), questions (how do I X), or anything else. Prefer request_limit_increase when the user is simply hitting a plan cap.

  Connector

• handoffs.partnership

  AI Design Blueprint

  Authenticated — creates a partnerships handoff record for design-partner, ecosystem, training, or advisory conversations needing human review. Persists a PartnershipHandoff row routed to the partnerships inbox; the user is contacted by the team. WHEN TO CALL: user explicitly wants to engage as a design partner, co-marketing/training partner, or evaluate the Blueprint for their org's training programme. ALWAYS confirm with the user before firing — this creates a human-visible partnerships ticket. WHEN NOT TO CALL: for general support / billing / access issues (use handoffs.operator); for paid-engagement enquiries (use handoffs.agency); proactively or as a sales prompt — only when the user has explicitly asked. BEHAVIOR: write-only, single insert, side-effecting (creates a ticket). Auth: Bearer <token> (any plan). UK/EU residency. Response confirms the ticket id + audience so the user can reference it.

  Connector

• get_savvly_faq

  savvly

  Get answers to frequently asked questions about Savvly. Use when the user has specific questions about how Savvly works, fees, withdrawals, or regulatory status. It is a convenience view of `search_savvly_content` scoped to the factual FAQ; for richer, audience-specific Q&As (employee / advisor / broker / employer), use `search_savvly_content` instead. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

  Connector

• check_balance

  PikaSim

  Returns the prepaid spending balance of the connected PikaSim agent wallet, in USD. Read-only; makes no changes. Call this before purchase_esim or purchase_phone_plan to confirm sufficient funds, or any time you need the current balance. Requires a connected agent wallet (OAuth or ak_live_ key). If no wallet is connected, the result explains how to connect one.

  Connector

• rendex_account

  Rendex: Rendering API for Images, PDFs & Content Extraction

  Check the Rendex account: which plan it's on, how many render credits have been used vs. the monthly limit (and when it resets), the per-minute rate limit, and a one-tap link to upgrade to a higher tier. Use this whenever the user asks about their usage, remaining quota, current plan, or how to get more renders / stop hitting limits. Read-only — costs no credits.

  Connector

• update_database_view

  remnus

  Rename a database view, change its icon, or patch fields within its existing config (filters, sorts, groupByCol, dateCol, cardProperties, etc — merged into the current config). The view's type (table/kanban/calendar) cannot be changed; create a new view instead. Use get_database_schema to find view ids and current config shape.

  Connector

• resolve_asset_id

  Sidecar

  Look up any data asset by name across the full catalog (dbt, Snowflake, BigQuery, Looker, etc.). Returns the asset's columns, description, owner, tags, and its **Sidecar asset identifier** (`asset_identifier` field) — the fully-qualified internal name used by lineage and impact tools (e.g. `model.jaffle_shop.fct_orders`, `PROD_DB.ANALYTICS.FCT_ORDERS`). When a single asset is resolved, the response also includes a `context_summary` with counts of linked tickets (Jira/Linear) and Slack threads. If those counts are non-zero and relevant to the user's question, follow up with `describe_asset` using include=['tickets'] or include=['slack'] to fetch the actual content. Call this first whenever the user refers to a specific table, model, view, or dashboard.

  Connector

• describe_asset

  Sidecar

  Fetch detailed information about a data asset by its identifier. Resolves the asset, then fetches the requested sections in parallel. Use this after advanced_search or resolve_asset_id to get deeper information about a specific asset. Sections: - overview: asset description, importance, owner, metadata - columns: full column schema with types and descriptions - tests: dbt test coverage (only for assets with a dbt parent) - context_counts: cheap count of linked tickets and Slack threads - tickets: full Jira/Linear ticket content - slack: full Slack thread content (truncated to first 5 messages per thread)

  Connector

• get_smart_folder

  linkedmash

  Get one smart folder (filtered view) by its slug — its name, description, filter query (base_query) and tabs (triage buckets). Use list_smart_folders first to find the slug. To read the posts inside, use get_smart_folder_posts.

  Connector

• precis_orientation

  Précis Finance MCP

  Call this first. Returns how to use Précis over this connector: the data model (scenarios, metrics, statements, dimensions), the reporting-tool variants, and how to build charts. Read it before composing queries.

  Connector

• handoffs.operator

  AI Design Blueprint

  Authenticated — creates a support handoff record when an agent needs human review, account-specific escalation, or operator follow-up that cannot be resolved with the read-only doctrine tools. Persists a SupportHandoff row (reason, topic, page_url, agent_name, agent_platform, trace_summary, user_email) routed to the support inbox; user is contacted by the team. WHEN TO CALL: user explicitly asks for human help, hits a billing/access issue, or the agent has tried the doctrine tools and the user still needs a human. ALWAYS confirm with the user before firing — this creates a human-visible ticket. WHEN NOT TO CALL: proactively, silently, or to log debugging traces (use diagnostic logs instead); for partnerships/agency enquiries (use handoffs.partnership / handoffs.agency); for content questions answerable by principles.search / guides.search. BEHAVIOR: write-only, single insert, side-effecting (creates a ticket the team will see). Auth: Bearer <token> (any plan). UK/EU residency. Response confirms ticket id + topic so the user can reference it.

  Connector