Mcp Workflow
Wire your coding agent into FluxTurn workflows by browsing connectors and templates instead of hand-rolling every third-party integration.
Overview
io.github.infoinlet-marketplace/mcp-workflow is a MCP server for the Build phase that lets agents browse 125 connectors and 234 templates and execute workflows via FluxTurn.
What is this MCP server?
- Browse 125 connectors and 234 workflow templates from the agent context
- Run automations through FluxTurn without leaving Claude Code or Cursor
- stdio npm package @infoinlet/mcp-workflow (v0.1.1) for local MCP registration
- Marketplace-sourced server aimed at AI-agent orchestration, not one-off scripts
- 125 connectors listed in server description
- 234 workflow templates listed in server description
- Server version 0.1.1 via npm stdio @infoinlet/mcp-workflow
What problem does it solve?
Agents can write code but struggle to discover and run vetted multi-app workflows without a curated connector and template index.
Who is it for?
Solo builders automating repetitive cross-app tasks (onboarding, alerts, data sync) from inside their agent IDE.
Skip if: Teams that only need a single REST integration with no workflow engine, or builders not using FluxTurn-compatible execution.
What do I get? / Deliverables
Your agent can list connectors and templates over MCP and kick off FluxTurn runs so integrations ship faster with less bespoke API glue.
- Agent-callable tools to search connectors and workflow templates
- Triggered FluxTurn workflow runs from natural-language or agent plans
- Reduced bespoke integration code for common multi-step automations
Recommended MCP Servers
Journey fit
Workflow automation sits in Build because solo builders compose product and ops glue—CRM, email, webhooks—while shipping, before Launch distribution concerns. Integrations is the canonical shelf for MCP servers that expose many external systems through one protocol surface.
How it compares
MCP workflow catalog and runner, not a single-purpose API skill or a GPU monitor.
Common Questions / FAQ
Who is mcp-workflow for?
Indie developers and agent-first builders who want FluxTurn workflows discoverable and runnable from Claude Code, Cursor, or similar MCP clients.
When should I use mcp-workflow?
Use it during Build and Operate when you are connecting SaaS tools and want templates instead of one-off integration code for every vendor.
How do I add mcp-workflow to my agent?
Register the stdio MCP server package @infoinlet/mcp-workflow in your client’s MCP config per the marketplace server.json, then restart the agent session.