iFlytek Workflow

iFlytek Workflow

Connect to iFlytek Workflow via the MCP server and run your own Agent.

26
Stars
4
Forks
0
Releases

Overview

iFlytek Workflow MCP Server is a simple MCP server implementation built to call iFlytek workflows via MCP tools. It enables intelligent workflow scheduling and execution, combining a structured workflow model with real-time data flow. The workflow is composed of multiple nodes and supports 14 node types (including basic, tool, logic, and transformation). By default, a workflow includes a Start Node (user input) and an End Node (output result). When triggered, workflows execute automatically according to predefined sequences and rules, requiring no manual intervention. Core capabilities include robust node support with complex variable I/O, and advanced orchestration modes such as sequential, parallel, loop, and nested execution, together with a Hook mechanism that enables streaming output for real-time processing. The system supports multiple development paradigms—single-turn, single-branch; single-turn, multi-branch; single-turn loop; and multi-turn interaction with context memory—providing flexibility for various use cases. For capability expansion, the platform offers Multi-Model Support based on the Model of Models (MoM) architecture, allowing flexible model choices at critical workflow stages. Usage involves MCP client integration, preparing a config.yaml, obtaining authentication, and publishing workflows as API.

Details

Owner
iflytek
Language
Python
License
MIT License
Updated
2025-12-07

Features

Robust Node Support

14 types of workflow nodes to meet diverse business requirements; supports complex variable I/O.

Advanced Orchestration Modes

Sequential, parallel, loop, and nested execution with a Hook Mechanism for streaming output and real-time processing.

Multiple Development Paradigms

Supports single-turn single-branch, single-turn multi-branch, single-turn loop, and multi-turn interaction with context memory.

Core Workflow Structure

Workflow includes a Start Node (user input) and an End Node (output).

Streaming Output via Hook Mechanism

Hook mechanism enables streaming output for real-time processing.

Multi-Model / MoM Capability

Model of Models (MoM) hybrid architecture enables multiple model choices at key workflow stages.

Audience

DevelopersIntegrate MCP-enabled workflows with iFlytek platforms and run agents efficiently.
EngineersEmbed MCP-enabled workflows into enterprise systems for automated agent orchestration.
Business usersSchedule and run automated workflows within business processes across teams.

Tags

MCPMCP serveriFlytekworkflowMoMModel of Modelsstreaming outputorchestrationnodesworkflow schedulingmulti-model