run_workflow

7 registry entries were observed exposing a tool named run_workflow — none of them flagged as a privileged capability.

Spelled run_workflow, run-workflow in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @sidebutton/server
   trust 60/100 · BMCP serverobserved 2026-08-18 · static extraction
   SideButton MCP server for AI agents — REST API, web dashboard, knowledge packs, and workflow engine
2. @alpacacloud/mcp
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   MCP server for Alpaca Cloud — AI agents connect to your project (Postgres, Auth, Storage), plus account-wide Sandboxes (code execution) and
3. io.github.AccelByte/ags-api-mcp-server
   trust 60/100 · BMCP serverobserved 2026-08-14 · static extraction
   Stateless MCP server for AccelByte Gaming Services APIs with OpenAPI integration
4. io.github.fetchsandbox/mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Stateful OpenAPI sandbox for AI agents to validate API integrations end-to-end.
5. io.github.hshintelligence/agent-scrape
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   Pay-per-call web scraping for AI agents via x402 on Base USDC. Six tools, no signup.
6. io.github.sidebutton/sidebutton
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Open-source MCP server with browser automation and knowledge packs for AI agents
7. slang-workflows
   trust 60/100 · BMCP serverobserved 2026-08-13 · static extraction
   Provable, declarative multi-agent workflows for Claude Code (typed .slang, non-LLM executor).

All indexed toolsSearch the registry for run_workflow