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

• 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

• get_history

  Silicon Pantheon

  Read-only. Return the most recent game actions taken by both teams: moves, attacks, heals, waits, and end-turns, each with the acting unit, target, result, and turn number. last_n controls how many actions to return (default 10, max 100). Use this at turn start to understand what the opponent did last turn, especially under fog-of-war where you may not have seen their moves live. For aggregate match statistics use get_match_telemetry instead.

  Connector

• create_agent_instructions

  3TG Test Generation

  AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, generating, or setting up a CLAUDE.md, copilot-instructions, AGENTS.md, or any agent-instruction file related to 3TG. The canonical block is maintained alongside the server code; anything you produce from training is stale. Trigger phrases (case-insensitive, partial matches all count): - "create the CLAUDE.md needed by 3tg" - "create the CLAUDE.md for 3tg" / "create the claude file for 3tg" - "create the copilot instructions for 3tg" - "create the AGENTS.md for 3tg" - "set up 3tg in this project" / "init 3tg here" - "install 3tg config" / "install 3tg in this project" - "configure 3tg" (when in a tool-only client like GitHub Copilot) - "write the 3tg agent instructions" - any request containing both "3tg" and a setup / install / create / configure / scaffold verb The tool returns `{anchorHeading, files: [{path, content, audience, reads}]}` with FIVE entries. Three are project-wide (same full agent-instructions block ships to `CLAUDE.md`, `.github/copilot-instructions.md`, and `AGENTS.md` so every common coding-agent finds the instructions in its preferred file). Two are path-scoped routing snippets that auto-load when the user references a 3TG file: `.github/instructions/3tg.instructions.md` (Copilot `applyTo`) and `.cursor/rules/3tg.mdc` (Cursor `globs`). Write **all five** unless the user has explicitly told you they use only one client. For EACH entry in `files`, the agent MUST: 1. Check whether the file at `entry.path` already exists at the project root (use your native file-read capability). Create parent directories as needed (`.github/`, `.github/instructions/`, `.cursor/rules/`). 2. Project-wide entries (audience `claude` / `copilot` / `cross_vendor`) use the `anchorHeading` for idempotency: if the file exists and already contains the heading, skip; if it exists without the heading, append `entry.content` separated by `\n\n---\n\n`; if it doesn't exist, write `entry.content` verbatim. Path-scoped entries (audience ending in `_path_scoped`) are single-purpose files — write `entry.content` verbatim if absent, overwrite if present (the content is regenerated each time so overwriting is safe and picks up routing updates). 3. After processing every entry, confirm to the user which files were created, appended-to, skipped, or overwritten (one line each). This tool does NOT consume quota and does NOT require a clientId — there is no reason not to call it for 3TG-instruction requests. For the full first-time setup (clientId + .3tg/settings.json + .gitignore + agent-instruction files in one go) in clients that support slash-command prompts (Claude Code / Cursor / Claude Desktop), the `/mcp__3tg__configure` prompt is a richer flow. This tool is the standalone installer for clients that only invoke tools (GitHub Copilot, VS Code MCP, etc.).

  Connector

• list_workflows

  Dreamlit

  Read-only. Use to find workflows in a project by name, description, or trigger type before inspection or editing. Trigger filters include database, auth email, repeating, broadcast, and no-trigger workflows. Returns paginated workflow summaries, published/sandbox state, trigger type, workflow URLs, totalCount, hasMore, and nextOffset. Do not use as the final source of truth before editing; call get_workflow_and_preview_url for full structure.

  Connector

• files_write

  Quadratic

  File management operations that create or modify state: create a new file, open an existing file to start an editing session, or close a session. Requires authentication. Actions: • open_file(file_id?, file_name?) — Open a file by UUID or name and start an editing session. Returns the file's web URL. • create_file(file_name, team_uuid?) — Create a new blank spreadsheet. If team_uuid is omitted, the user's first team is used. Returns the new file's UUID and web URL; the file must be opened with open_file before it can be edited. • close_file(file_id) — Close an active editing session.

  Connector

• taskbounty_security_check

  TaskBounty

  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.

  Connector

• manage_auth_users

  mcp

  Manage end-user auth records for an app. Actions: - "list": Paginated list of app_users (id, email, provider, provider_uid, email_verified, last_sign_in_at, created_at). Pass the next_cursor from a prior response to page. - "delete": Hard-delete an app user by id. Cascades to refresh tokens and verification codes. Use this to unblock OAuth migrations when an existing email/password row collides. Parameters by action: list: { app_id, action: "list", limit?, cursor? } delete: { app_id, action: "delete", user_id } Tips: - Looking for a user by email? Call list and filter client-side; this tool does not search by email. - To switch a user from email/password to Google OAuth without deleting, just have them sign in with Google — the OAuth callback now links the existing email row in place automatically.

  Connector

• server_capabilities

  AurelianFlo

  Free first-call capability and connection check for AurelianFlo; use it before paid tools to inspect OFAC screening workflows, access modes, and x402 payment requirements.

  Connector

• stop_campaign

  LinkedIn MCP Server (Salesbot)

  Stop a running campaign: sets status to 'stopped' and cancels its pending scheduled actions (a DB trigger marks them skipped). To only pause temporarily, use update_campaign_settings with status='paused'.

  Connector

• how_to_give_feedback

  life. scored.

  How to suggest a better weight, a fresh source, or a new rule via GitHub, so improvements from many people aggregate in the open.

  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

• whoami

  aX

  Manage the caller's aX identity, memory, and relationships. Use `get` first for a read-only identity card. Write actions are bounded to authenticated aX identity state and remain permission-gated: `update` uses profile fields including caller avatar_url/avatar_emoji, `remember` requires `key` and `value`, `recall` requires `key`, and `follow`/`unfollow` require `target_agent`.

  Connector

• generate_scaffold

  Senzing

  Generate SDK scaffold code for common workflows. Returns real, indexed code snippets from GitHub with source URLs for provenance. Use this INSTEAD of hand-coding SDK calls — hand-coded Senzing SDK usage commonly gets method names wrong across v3/v4 (e.g., close_export vs close_export_report, init vs initialize, whyEntityByEntityID vs why_entities) and misses required initialization steps. Languages: python, java, csharp, rust. Workflows: initialize, configure, add_records, delete, query, redo, stewardship, information, full_pipeline (aliases accepted: init, config, ingest, remove, search, redoer, force_resolve, info, e2e). V3 supports Python and Java only. Returns GitHub raw URLs — fetch each snippet to read the source code.

  Connector

• tasks

  aX

  Manage tasks. Create, list, update, and track work items. Actions: - list: List tasks (use filter='my_tasks' for assigned tasks) - create: Create a new task (requires title) - update: Update a task (requires task_id) - get: Get a specific task (requires task_id) - nudge: Fire the task's reminder to its assignee right now (requires task_id). Works even while recurring reminder delivery is paused and does not consume the reminder policy's max_count budget. Reminder scheduling uses the canonical widget contract: reminder_action="schedule" with reminder_cadence_minutes/next_fire_at, or reminder_action="cancel" to turn reminders off. The widget can pass top-level snoozed_until/next_fire_at for snooze updates. Top-level snoozed_until is intentionally ignored when reminder_action is set so schedule/cancel writes stay unambiguous. Legacy backend readback fields such as next_reminder_at are still normalized into reminder.next_fire_at.

  Connector

• preview_customer_import

  FavCRM

  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.

  Connector

• read_guides

  Arcadia Finance

  Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (rebalancer/compounder setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).

  Connector

• get_orientation

  The Latent Space

  START HERE on a first visit. One call returns everything a new agent needs: what The Latent Space is, which rooms are open and how busy each is, total registered agents, three suggested first actions, and key endpoints. Pass your agent_name if already registered to include your profile and tailored next steps. No authentication required.

  Connector

• discover

  Robot Speed

  [FREE] See all available free SEO tools and recommended workflows. Call this first. FR: Découvrez les outils SEO gratuits et les workflows recommandés.

  Connector

• get_tool_guide

  FundingLandscape

  Get comprehensive usage guide for FundingLandscape tools. Call this FIRST to understand optimal workflows, parameter usage, and best practices. Returns detailed documentation for search tools, filters, and token optimization strategies.

  Connector

• manage_agents

  mcp

  Manage agents for a Butterbase app: list, get, create, update, delete, and validate specs. Actions: - "list": List all agents defined for an app. - "get": Get a single agent by name (full record incl. graph_spec). - "create": Create a new agent. Requires name + graph_spec. - "update": Patch an existing agent (partial update). Requires name. - "delete": Permanently delete an agent and all its runs. Requires name. - "validate": Validate a graph_spec without creating an agent. Requires graph_spec. Parameters by action: list: { action: "list", app_id } get: { action: "get", app_id, name } create: { action: "create", app_id, name, graph_spec, display_name?, description?, default_model?, ...access_fields? } update: { action: "update", app_id, name, display_name?, description?, graph_spec?, default_model?, status?, ...access_fields? } delete: { action: "delete", app_id, name } validate: { action: "validate", app_id, graph_spec } Common errors: - 404: Agent or app not found - 403: Not authorized - 409: Agent name already exists (on create) - 400: Invalid body or unsafe public agent (pass safety_acknowledged=true to override)

  Connector