Mcp Workflow

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Workflow automation for AI agents — browse 125 connectors + 234 templates, run via FluxTurn.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server for workflow automation that lets an assistant browse connectors and templates and run workflows through FluxTurn.

What you can do
Browse a catalog of connectors and templates for workflow automation, according to the registry description. Run workflows through FluxTurn, the execution service named in the description. The manifest lists no individual tools, so the exact operations an assistant can call are not documented here.
When to use it
Worth considering when you want an assistant to help assemble or trigger automated workflows from prebuilt connectors and templates rather than writing integrations yourself.
Requirements
Runs as a local process over stdio, installed from the npm package @infoinlet/mcp-workflow, so a Node.js runtime is needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The description names FluxTurn as the execution service, so workflow runs and any data they carry may go to that third party; confirm what is sent before using real data. No credentials are declared, but the actual tool behavior is undocumented, so review what the server does before relying on it.

Installation

In SourceWeft

  1. Open Mcp Workflow in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.