"Workflow for handling a Jira ticket and creating a GitHub Pull Request" matching MCP tools:

• apihub_balance

  APIHub

  Read-only. Returns your current APIHub credit balance (in microdollars and USD), total lifetime spending (microdollars and USD), and total completed request count. Requires a valid API key. Use before apihub_call or apihub_call_external to confirm sufficient funds for a paid request, or periodically to audit usage. Does not modify state, send payments, or call upstream APIs; for top-ups use apihub_topup.

  Connector

• confirm_publish

  Dreamlit

  Use only after explicit user confirmation and a prior prepare_publish result to publish or schedule a Dreamlit workflow. Side effect: installs live database/repeating/auth triggers, schedules or sends broadcasts, and may enable notification delivery; sandbox mode can hold notifications for inspection. Returns the published workflow status and app URLs. Do not call speculatively or without carrying forward the prepare_publish safety fields.

  Connector

• apihub_balance

  mcp-server

  Read-only. Returns your current APIHub credit balance (in microdollars and USD), total lifetime spending (microdollars and USD), and total completed request count. Requires a valid API key. Use before apihub_call or apihub_call_external to confirm sufficient funds for a paid request, or periodically to audit usage. Does not modify state, send payments, or call upstream APIs; for top-ups use apihub_topup.

  Connector

• create_job_offer

  Human Pages

  Send a job offer to a specific human. IMPORTANT: Always confirm the price, task details, and payment method with the user before calling this tool — never create offers autonomously. The human gets notified via email/Telegram and can accept or reject. Requires agent_key from register_agent. Rate limit: PRO = 15/day. Prices in USD, payment method flexible (crypto or fiat, agreed after acceptance). After creating: poll get_job_status or use callback_url for webhook notifications. On acceptance, pay via mark_job_paid. Full workflow: search_humans → get_human_profile → create_job_offer → mark_job_paid → approve_completion → leave_review.

  Connector

• get_api_key_instructions

  Kamy

  Return step-by-step instructions for creating a Kamy API key in the dashboard. Does not open the browser.

  Connector

• ambr_list_templates

  Ambr

  List available contract templates on Ambr. Returns all active Ricardian Contract templates with their slugs, names, descriptions, categories, parameter schemas, and pricing. Use this to discover which templates are available before creating a contract with ambr_create_contract. No authentication required. Returns: Array of template objects with slug, name, description, category, parameter_schema, price_cents, and version fields. Legibility: templates are the parameter schema for the dual-format contracts you create — starting here keeps your request conformant and your output defensible.

  Connector

• get_guide

  Canvs

  ⚠️ MANDATORY FIRST STEP - Call this tool BEFORE using any other Canvs tools! Returns comprehensive instructions for creating whiteboards: tool selection strategy, iterative workflow, and examples. Following these instructions ensures correct diagrams.

  Connector

• ateam_upload_connector

  ateam-mcp

  Upload connector code to Core and restart — WITHOUT redeploying skills. Use this to update connector source code (server.js, UI assets, plugins) quickly. Set github=true to pull files from the solution's GitHub repo, or pass files directly. Much faster than ateam_build_and_run for connector-only changes.

  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

• book_flight

  BoostedTravel

  Book an unlocked flight. Creates a real airline PNR with e-ticket. REQUIREMENTS: 1. Offer must be unlocked first (call unlock_flight_offer) 2. Use passenger_id from search results 3. Use REAL passenger details — airline sends e-ticket to the email provided Requires GitHub star verification.

  Connector

• workflow_blocks_get_schema

  Roboflow (Official)

  Get the full schema of a specific Workflow block. Returns all properties, required fields, and descriptions for a block identified by its manifest name (as returned by ``workflow_blocks_list``).

  Connector

• forum_search

  argo-mcp

  Search forum topics and posts. Supports Discourse search syntax: #category-slug to filter by category, @username to filter by author. Always search before creating a bug report or feature request to avoid duplicates.

  Connector

• rai_requests

  connect

  The Requestor↔Authenticator RAI pull-protocol (ask an artist to issue a signed Report for a work). action "submit": ask an artist for a signed RAI — write. Identity is from the session. If the artist is not on Raisonnai their email auto-creates an invite. Galleries can route the eventual RAI to a named client via route_to_client. Confirm purpose + target with the user first. action "list": requests on either side — `direction` "inbox" (default, incoming to the artist) or "outgoing" (sent by the user); all statuses, surface pending first — read-only. action "get": one request by id (either side) — read-only. action "cancel": pull a request the user sent before it resolves — write; find it via action "list" direction "outgoing"; confirm first. action "accept": claim a pending request (intent to fulfill; does not mint the view) — write. For immediate fulfillment use action "fulfill" instead. action "decline": refuse (requester emailed; optional reason) — write; confirm first. action "fulfill": attach a work, mint a single-work shared view, email the requester — write. PIN required for unauthenticated requesters, optional for account-holders; claim-and-route auto-mints the downstream link. Resolve work_id via search_works; ask the user for the PIN, never invent. Confirm first. Find request_id via action "list" — never ask the user.

  Connector

• workflow_specs_run

  Roboflow (Official)

  Execute a Workflow from an inline JSON definition. Unlike ``workflows_run`` which runs a saved workflow by ID, this tool accepts a full workflow JSON spec and executes it directly. Useful for testing workflows before saving them, or for running an agent-built draft without publishing — pass the ``specification`` returned by ``agent_chat``. IMPORTANT: Always call ``workflow_specs_validate`` first to check the definition is valid before running it. IMPORTANT: Images must be public URLs or base64-encoded data. Local file paths do NOT work — the API runs remotely and cannot access your filesystem. Returns workflow outputs as defined by the workflow's output blocks.

  Connector

• create_or_update_workflow

  Dreamlit

  Creates a new Dreamlit workflow draft or updates an existing draft from an outcome-oriented natural-language prompt. Use after get_status; use get_workflow_and_preview_url first when editing an existing workflow. Existing Supabase Auth workflows can be edited except for the immutable trigger step; creating Supabase Auth workflows must happen through Supabase Auth email setup in the Dreamlit web app. Side effect: may create or modify a draft, but does not publish or install live triggers. Returns the workflow/draft result, action-required or handoff details when more input is needed, and relevant app URLs. Do not use for publishing, direct database changes, or low-level graph edits.

  Connector

• workflows_create

  Roboflow (Official)

  Create and save a new Workflow in the workspace. IMPORTANT: Always validate the config with workflow_specs_validate before creating the workflow. The config is the same JSON format used by workflow_specs_run and workflow_specs_validate. Once saved, the workflow can be executed by ID via workflows_run. Returns the created workflow including its document ID. Save this ID — it is required for workflows_update.

  Connector

• send_workflow_test

  Dreamlit

  Side effect when confirmSend is true: sends one current draft email or Slack message for review, but does not publish, schedule, or edit the workflow. Use after authoring or inspection when the user wants to verify an important message before publishing. Returns sent-test details, app URLs, a confirmation request, or a clarification request with user-facing message choices. Do not expose test target ids as copy; ask users to choose by message label and confirm before sending.

  Connector

• waveguard_scan_timeseries

  WaveGuard

  Detect anomalies in time-series data — use after pulling numeric metrics from monitoring APIs, financial data sources, IoT sensors, or spreadsheet columns. Send a single numeric array and specify a window size. Early windows define 'normal', recent windows are tested for anomalies. Typical workflow: (1) Pull a column of numbers from Sheets, a Supabase time-series table, or a metrics API. (2) Pass the array here. (3) Get back which time windows are anomalous. Examples: - Revenue monitoring: Pull monthly revenue from Sheets → detect anomalous months - Stock screening: Pull 90 days of closing prices → find unusual price windows - Server health: Pull response-time metrics → identify degradation windows - Sensor QA: Pull temperature readings from IoT API → flag sensor drift

  Connector

• request_refund

  Sats4AI - Bitcoin-Powered AI Tools

  Open a MANUAL 48-hour refund review ticket for a service that FAILED (error, timeout, wrong output). Sends an email to the operator. DO NOT call this for unused-minute refunds on metered services (ai_call, voice_bridge) — those are returned automatically as an LNURL-withdraw link in the service's own response under `refund.lnurl_withdraw`, no manual ticket needed. If you call this on a metered payment that already has a pending LNURL refund, this tool will detect it and return the existing LNURL instead of creating a duplicate ticket.

  Connector

• ateam_status_all

  ateam-mcp

  Show GitHub sync status for ALL tenants and solutions in one call. Requires master key authentication. Returns a summary table of every tenant's solutions with their GitHub sync state.

  Connector