Skip to main content
Glama
676,627 tools. Updated 2026-10-19 12:50

"How to manage and create GitHub Actions workflows" matching MCP tools:

  • Update a transaction automation rule. Only provided fields change; conditions and actions are replaced wholesale, not merged. Setting isEnabled to true or changing conditions/actions re-validates every referenced category, tag, payee, and account and clears pausedReason, so this is how a rule paused by a deleted reference is repaired. Position is not changed here, use reorder_transaction_automations. Requires finance:write scope.
    ConnectorOAuth
  • Scan a PUBLIC GitHub repo for GitHub Actions + CI security/maintenance hygiene before launch — ideal for apps built with Lovable, Bolt, Replit, Cursor, or v0 ("is my AI-built app safe to ship?"). Returns a safe summary: findings by category with counts, an unlisted report URL, and fix options. SCOPE, honestly: it checks GitHub Actions workflow + update-automation hygiene only — it does NOT check exposed secrets, auth, payments, webhooks, or runtime behavior, which need a manual review. No API key required. For PRIVATE repos, tell the user to run `npx taskbounty-check .` locally so their source never leaves their machine.
    ConnectorNo auth
  • Manage a campaign by pausing or restarting it. KEYWORDS: pause, stop, restart, resume, unpause, campaign, control, manage, halt WHEN TO USE: - User asks to "pause campaign X" - User wants to "stop campaign Y" - User requests to "restart campaign Z" - User wants to "resume campaign A" - User asks to "unpause campaign B" ACTIONS: - pause: Temporarily pause an active campaign to stop ad serving and budget spend - restart: Resume a paused campaign to continue ad serving and budget spend REQUIRED PARAMETERS: - campaign_id: The unique identifier of the campaign to manage (integer, required) - action: The action to perform - "pause" or "restart" (string, required) CAMPAIGN ID SOURCES: Campaign IDs can be obtained from: - search_campaigns_by_names tool - create_campaign tool response - Campaign management interface URLs IMPORTANT VALIDATION REQUIREMENTS: - **CRITICAL**: You can ONLY pause campaigns that are currently "Active" - **CRITICAL**: You can ONLY restart campaigns that are currently "Paused" - Before attempting to pause or restart, use search_campaigns_by_names to verify the current campaign status
    Connector
    Destructive
    API key
  • List and search Rigor workflows for your organization, with filtering and pagination. Returns status, progress, capacity usage, and available actions per workflow. Use to monitor workflow state, understand concurrent limit usage, identify stuck or completed workflows, and — via q — find prior work on a subject before commissioning it again. Pair a q hit with rigor_status to read that workflow's deliverable.
    ConnectorNo auth
  • Install an exact marketplace module version into an application and create any missing installed-template actions. Requires the manage_automation permission. Call get_module_catalog first to select the module and version, then get_module_details after installation to inspect setup requirements and installed action references. Safe to re-run: installing a version that is already installed only fills in missing template actions rather than duplicating them. Modules with manual setup fields still need an operator to enter credentials in the dashboard before their actions will run.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.

  • Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.

  • Given one package and two versions (from -> to), returns a structured upgrade analysis: semver classification, GitHub release notes summary, detected breaking changes, security advisories fixed in the range, migration guide links, and a clear recommendation. Use when the user asks about a specific package upgrade ('what changed between react 18 and 19', 'is it safe to bump axios from 0.27 to 1.0', 'what does upgrading lodash 4.17.20 to 4.17.21 fix'). Supports npm, pypi, and github-actions (use the action reference as the name, e.g. actions/checkout). For analyzing many packages at once or a Dependabot batch, use analyze_packages_bulk instead.
    ConnectorNo auth
  • Discover the AdKit MCP contract with progressive drill-down. Top-level paths: "manage" (campaigns, accounts, and reporting across Meta, Google, TikTok, Reddit, X, and LinkedIn, plus Microsoft and ChatGPT Ads raw access and drafts), "integrations" (read-only GA4 data), "library" (browse ads, advertisers, and inspiration boards), and "studio" (AI static ad generation). Start with adkit_help() for the root overview, or drill down like adkit_help({ path: "manage google campaigns create" }). A keyword search with q, e.g. adkit_help({ q: "keyword planner" }) → "manage google research keywords", covers the full command catalog: a capability missing from one drill-down path may still exist under another.
    ConnectorAPI key
  • File a ticket, message, event or draft for a person to approve. Nothing runs yet. Use it when the user asks you to create a Jira, Linear or GitHub issue, post to Slack, book a calendar hold, draft an email, add a Notion page or a Zendesk note. The proposal goes to the workspace's approval queue, where a person picks the target (project, channel, recipient), edits it if needed and approves; only then does it run. Gmail actions only ever save a draft. Over MCP you cannot approve or run anything; check the queue with ``list_proposed_actions`` first to avoid duplicates. Returns ``{id, action_type, status: "proposed"}``, ``{error: "duplicate", existing_id}`` if the same one is already waiting, or ``{error}`` if actions are not switched on for your account.
    ConnectorAPI key
  • Create or query data in an AiAkiv app. Use this when the user asks to make or look up something in an AiAkiv app, or to manage their AiAkiv account through the `console` app: teams and invitations, org links, audit logs, save-target history, switching Main or turning it off and on, project presets, and the cards they created. Do not use it to save a memory; use `save_memory` for that. Cards are made with `create_aiakiv_card`. Writes when `action="create"`. Some apps publish the result to the open web: the returned link is live the moment it comes back — unlisted, but reachable by anyone holding the address — and that publication cannot be undone from here. The content is written by the caller from memory the user can already read; the server never calls a model. Args: app: The app name. An unknown one returns `available_apps`. action: `"describe"` returns the app's field list and limits, which is how the exact input shape for an app is established; `"create"` writes. Apps may define further read actions, which `describe` lists. data: The app's payload — a JSON object, or a JSON string holding one. The string form survives transports that mangle long multi-line fields. Returns: `{ok, app, key, url, notice?}` on create, or `{error, hint}`. The returned `url` is the link to the created item. A `notice` is the app stating what just became public and how to undo it, which is information the user needs to see rather than a detail to compress away. On a shape error the app names the offending field.
    Connector
    Destructive
    OAuth
  • List the approval workflows this workspace can use (company-wide ones plus workspace-bound ones), with their steps and named approvers. Workflows are created in the OmniSocials dashboard (Approvals); this tool only lists them. Pass a workflow's id as `approval_workflow_id` on create_post to hold a scheduled post for review: it is created as `in_approval`, the approvers are notified, and it publishes at schedule_at once the last step approves. Call this first when the user wants agent-created posts to be reviewed/approved before publishing; if the list is empty, tell the user to create a workflow under Approvals in the dashboard.
    ConnectorOAuth
  • List the project workflows this workspace offers, with their stages, availability and how many projects run on each. Use it to explain what kinds of project exist; for actual projects use twelfth_list_projects.
    ConnectorOAuth
  • Site admins only (needs an 'admin'-scoped token). Import a third-party GitHub Action at ONE tag, branch or full commit SHA into the Gluecron mirror namespace (gluecron-actions/<owner>--<repo>), so workflows that say `uses: owner/repo@ref` can run it. Workflow runs never fetch from github.com; an action that is not imported is skipped. Re-importing the same ref updates it to what upstream has now. Audit-logged. Returns {action, ref, sha, previousSha, mirror, upstreamUrl, hasActionYml}.
    ConnectorNo auth
  • Preview a bulk customer import (max 2000 rows). Matches existing accounts by phone/email and shows create vs update actions plus points/stamps/credit deltas. Use commit_customer_import with the returned sessionId to apply.
    ConnectorNo auth
  • Preview a bulk customer import (max 2000 rows). Matches existing accounts by phone/email and shows create vs update actions plus points/stamps/credit deltas. Use commit_customer_import with the returned sessionId to apply.
    ConnectorNo auth
  • Create a workflow — a multi-step document pipeline (workflows group): parse → extract/classify/split → validations → human review. name alone creates an empty draft; steps builds the graph up front (call get_documentation with https://docs.extend.ai/workflows/configuring-workflows.md before hand-authoring a step graph). The draft is the only mutable surface — edit with update_workflow, freeze with deploy_workflow_version, run with run_workflow.
    ConnectorOAuth
  • What the user has connected, and what they could connect. Returns every integration available to this account with `connected` true/false, the accounts behind it, the tools it unlocks, and the URL to connect or manage it. Call this BEFORE telling anyone to connect anything, and before saying a source is unavailable: guessing is how the assistant has told people to connect accounts they already had. An integration missing from the list is not offered to this user at all, so do not suggest it. `suggested` is what is worth connecting next, best first, each with the payoff in the user's terms: use it when asked what would help, and lead with the first one rather than listing the shelf. Connecting is a browser grant: hand the user the URL, never claim to have done it. Each row's `steps` is how to connect it: when someone asks how, walk them through those steps and link `url`, which is that integration's page. Services that are not native integrations (Notion, GitHub, Stripe, Linear and dozens more) are connectors: call list_connectors.
    ConnectorNo auth
  • Read project context in exactly six domains: code, system (architecture, data model, APIs, roadmap), issues, backlog (epics and tasks), agent skills, and stack layers. Most actions read stored, indexed context such as the knowledge graph. Two reads reach GitHub live: issues/read returns the current GitHub issue and latest comments (issues/context, list and overlap use stored issue context), and code/read can fetch file content from repositories connected to the organization. Use backlog list/get actions to find existing epic and task IDs before calling update_backlog. Read-only: it does not create, change, or delete backlog, workflow, or GitHub data. Not for workflow runs or task executions: use list_workflow_runs to discover runs, get_workflow_run for a known run ID, and get_task_execution for an execution ID returned by start_task.
    ConnectorAPI key
  • Explain how Australian home-loan rates are determined and the next step. Manage Your Loans does not publish live rates; a broker compares them for a specific scenario.
    ConnectorNo auth
  • Show the org's plan, effective entitlements, current usage, and which upgrade actions are available. Read this if a create action was refused with a plan limit — it names the limit you hit and how to lift it. Returns { plan, subscription, promo, entitlements, usage, overrides, enforced, manage } — `enforced: false` means plan limits are not currently applied, and `manage` carries the upgrade paths.
    ConnectorNo auth
  • Classifies a supplied request as help, action, correction or unsupported. Classification covers read, create, update, delete, correct, undo, reverse, email and batch actions, including creating a sales invoice or add a customer, plus help wording such as how do I. Action results include allowed tools and an opaque routeToken. Help and correction results do not issue transactional route tokens.
    ConnectorNo auth