SkillAgentSearch skills...

recursive-flow

Agentic workflow automation server for MCP. Enables AI assistants to break down complex tasks into actionable steps, orchestrate tool execution, and track progress autonomously.

Install / Use

claude mcp add fritzprix -- npx -y github:fritzprix/recursive-flow

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

73/100

Category

Automation

Supported Platforms

Claude Code
Claude Desktop

Our assessment of recursive-flow

recursive-flow scores 73/100 on our quality scale, 2635th of 2,877 Automation skills we index.

Its MCP Server is 13 KB long, well organised into 32 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
5/15

Maintenance, license and trust

  • The repository was last updated about 15 months ago. Expect some instructions to reference tool versions or APIs that have since changed.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-19. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

recursive-flow compared with similar skills

All 4 of these similar skills score higher than recursive-flow; compare them before choosing.

SkillScoreStarsUpdatedFormat
recursive-flow (this skill)by fritzprix73315mo agoMCP Server
Agent-Reachby Panniantong100109.5k1d agoCLAUDE.md
headroomby headroomlabs-ai10079.0ktodayCLAUDE.md
CowAgentby zhayujie10047.8ktodayCLAUDE.md
Scraplingby D4Vinci10098.3ktodayMCP Server

Frequently asked questions

How do I install recursive-flow?
Run claude mcp add fritzprix -- npx -y github:fritzprix/recursive-flow. The install tabs above show the steps for each supported agent.
Which AI agents does recursive-flow work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is recursive-flow safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is recursive-flow still maintained?
The repository was last updated about 15 months ago. Expect some instructions to reference tool versions or APIs that have since changed.

Recursive Flow: AI Agent Workflow Manager

Recursive Flow is a powerful MCP (Model Context Protocol) server that enables AI agents to break down complex tasks into manageable steps and execute them systematically. Perfect for automating multi-step workflows with Claude Desktop and other MCP-compatible AI assistants.

What It Does

  • Smart Task Breaking: Automatically breaks down complex requests into smaller, manageable todo items
  • Guided Execution: Provides step-by-step guidance to AI agents on what to do next
  • Tool Orchestration: Coordinates multiple tools and services to complete complex workflows
  • Progress Tracking: Keeps track of what's been done and what's still pending
  • Context Preservation: Maintains full context throughout the entire workflow

Key Benefits

  • Autonomous Operation: AI agents can work independently without constant guidance
  • Reliable Execution: Systematic approach ensures nothing gets missed
  • Flexible Integration: Works with any MCP-compatible tools and services
  • Complete Transparency: Full audit trail of all actions taken
  • Self-Managing: Agents know exactly what to do next at each step

How It Works

When you give your AI assistant a complex task, Recursive Flow helps it work through the task systematically:

  1. Planning Phase: The AI breaks down your request into specific action items
  2. Execution Phase: Each action item is tackled step-by-step with the right tools
  3. Progress Tracking: The system keeps track of what's done and what's next
  4. Completion: Once all items are finished, you get a complete summary

Example Workflow

Let's say you ask your AI to "Research competitors and create a market analysis report":

  1. Planning: The AI creates a plan with steps like:

    • Research main competitors
    • Analyze their pricing strategies
    • Compare product features
    • Create summary document
  2. Execution: For each step, the AI:

    • Identifies the right tools to use (web search, data analysis, document creation)
    • Executes each tool in the right order
    • Records the results for the next step
  3. Completion: You receive a comprehensive market analysis with all supporting research

Recursive Flow Architecture

The following sequence diagram shows how the tools work together in a recursive, self-managing workflow:

@startuml
title Recursive Flow: Agentic Workflow Management

participant User
participant Agent
participant "Recursive Flow" as RF
participant "External Tools" as Tools

== 1. Workflow Initiation ==
User -> Agent: "Complex task request"
Agent -> RF: startJob(goal)
RF -> Agent: {context: {id, goal, status:'planning'}, nextAction: 'setPlan'}

== 2. Planning Phase ==
Agent -> RF: setPlan(jobId, todos)
RF -> Agent: {context: {todos: [...]}, nextAction: 'selectNextTodo'}

== 3. Recursive Execution Loop ==
loop For each TODO item
    Agent -> RF: selectNextTodo(jobId)
    RF -> Agent: {context: {currentTodo: {...}}, nextAction: 'planTodoExecution'}

    Agent -> RF: planTodoExecution(jobId, tools)
    RF -> Agent: {context: {toolPlan: [...]}, nextAction: 'tool1'}

    loop For each tool in toolPlan
        Agent -> Tools: execute_tool(params)
        Tools -> Agent: tool_result
        Agent -> RF: reportExecution(jobId, tool, result)
        alt More tools remaining
            RF -> Agent: {context: {executionHistory: [...]}, nextAction: 'next_tool'}
        else All tools completed
            RF -> Agent: {context: {executionHistory: [...]}, nextAction: 'completeTodo'}
        end
    end

    Agent -> RF: completeTodo(jobId, todoId)
    alt More TODOs remaining
        RF -> Agent: {context: {todos: [✓,○,○]}, nextAction: 'selectNextTodo'}
    else All TODOs completed
        RF -> Agent: {context: {todos: [✓,✓,✓]}, nextAction: 'finishJob'}
    end
end

== 4. Workflow Completion ==
Agent -> RF: finishJob(jobId)
RF -> Agent: {context: {status: 'complete', finalReport: '...'}, nextAction: null}
Agent -> User: "Complete results with full context"

@enduml

Key Architectural Features

  • Self-Directed: Each tool returns nextAction to guide the agent
  • Context Accumulation: executionHistory builds comprehensive knowledge
  • Variable Length: Workflow adapts to any number of steps and tools
  • Recursive Pattern: Core loop of select → plan → execute → complete
  • Clean Termination: nextAction: null signals workflow completion

What Makes It Special

  • No Manual Intervention: Once started, the AI can complete complex multi-step tasks without you having to guide each step
  • Reliable Results: The systematic approach ensures consistent, thorough completion of tasks
  • Full Visibility: You can see exactly what was done and how decisions were made
  • Extensible: Works with any tools your AI assistant has access to

Installation & Setup

Quick Setup with Claude Desktop (Recommended)

Note: Make sure the package is published to npm before using npx. If not published yet, use the "Local Development Setup" method below.

The easiest way to use Recursive Flow is with npx, which automatically downloads and runs the latest version:

  1. Locate your Claude Desktop configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add Recursive Flow to your MCP servers configuration:

{
  "mcpServers": {
    "recursive-flow": {
      "command": "npx",
      "args": ["recursive-flow"],
      "env": {}
    }
  }
}
  1. Restart Claude Desktop

That's it! Claude will automatically download and run Recursive Flow when needed.

Alternative Setup Methods

Option 1: Global Installation

npm install -g recursive-flow

Then configure Claude Desktop:

{
  "mcpServers": {
    "recursive-flow": {
      "command": "recursive-flow",
      "args": [],
      "env": {}
    }
  }
}

Option 2: Local Development Setup

If you want to run from source code:

git clone [repository-url]
cd recursive-flow
npm install
npm run build

Then configure Claude Desktop:

{
  "mcpServers": {
    "recursive-flow": {
      "command": "node",
      "args": ["/absolute/path/to/recursive-flow/dist/index.js"],
      "env": {}
    }
  }
}

Verification

After setup, restart Claude Desktop and ask it to use Recursive Flow:

"Can you start a job to research competitors in the AI industry?"

If configured correctly, Claude will use the startJob tool to begin a workflow.

Publishing to NPM

If you're the package maintainer, here's how to publish for npx usage:

# Build the package
npm run build

# Test locally first
npm pack
npm install -g ./recursive-flow-1.0.2.tgz

# Publish to NPM
npm publish

After publishing, users can immediately use npx recursive-flow without any installation.

Using with Other AI Assistants

Recursive Flow works with any AI assistant that supports the Model Context Protocol (MCP). Check your AI assistant's documentation for MCP server setup instructions.

How to Use

Once installed, you can give your AI assistant complex tasks and it will automatically use Recursive Flow to manage the workflow. Here are some examples:

Simple Usage

Just ask your AI assistant to handle complex tasks naturally:

"I need you to research the top 5 competitors in the electric vehicle market and create a detailed comparison report"

What Happens Behind the Scenes

  1. Job Creation: The AI starts a new workflow job
  2. Planning: Breaks down the task into specific steps
  3. Execution: Works through each step systematically
  4. Completion: Provides comprehensive results

Example Tasks Perfect for Recursive Flow

  • Market Research: "Research competitors and create analysis reports"
  • Content Creation: "Plan and create a complete social media campaign"
  • Data Analysis: "Analyze sales data and prepare executive presentations"
  • Project Planning: "Create a detailed project timeline with milestones"
  • Research Projects: "Investigate a topic and compile comprehensive findings"

Available Tools

Recursive Flow provides these tools for AI agents (in execution order):

  • startJob: Begin a new workflow with a specific goal
  • setPlan: Break down the goal into actionable steps
  • selectNextTodo: Choose the next task to execute
  • planTodoExecution: Plan how to execute a specific task
  • reportExecution: Record the results of task execution
  • completeTodo: Mark a task as finished
  • finishJob: Complete the entire workflow (needs implementation)

Flow Pattern

The tools follow a recursive pattern:

  1. Start → setPlan → selectNextTodo
  2. Loop: selectNextTodo → planTodoExecution → [external tools] → reportExecution → completeTodo → selectNextTodo
  3. End: selectNextTodo → finishJob → null (workflow complete)

Benefits for Users

  • Save Time: No need to break down complex tasks manually
  • Ensure Completeness: Nothing gets missed in multi-step processes
  • Track Progress: See exactly what's been done and what's remaining
  • Reduce Errors: Systematic approach minimizes mistakes
  • Work Autonomously: AI handles complex workflows independently

Troubleshooting

Common Issues

Claude doesn't recognize Recursive Flow tools:

  • Check that the MCP server configuration uses npx and recursive-flow correctly
  • Ensure you have an internet connection (npx needs to download the package)
  • Restart Claude Desktop after configuration changes
  • Try running npx recursive-flow in terminal to verify it works

NPX-related issues:

  • If you get "command not found", ensure Node.js and npm are installed
  • For the first run, npx might take a moment to download the package
  • If download fails, try: npm cache clean --force then restart Claude

Tasks aren't being broken down properly:

  • Try being more specific about what you want to achieve
  • Break very large tasks into smaller initial requests

Performance issues:

  • The first run might be slower as npx downloads the package
  • Subsequent runs will be faster as the package is cached

🤖 System Prompt for LLM Agents

Use this prompt to instruct your LLM agent on how to interact with Recursive Flow.

System Prompt Template

You are an autonomous workflow agent using the Recursive Flow MCP server.
Follow this exact protocol to handle complex multi-step tasks:

1. **Job Initialization**
   - Start by calling `startJob` with the user's main goal
   - Extract the `jobId` from the response

2. **Planning Phase**
   - Call `setPlan` with the `jobId` and an ordered array of todo descriptions
   - Each todo should be a clear, actionable step toward the goal

3. **Execution Loop**
   For each todo:
   - Call `selectNextTodo` with the `jobId`
   - When a todo is selected, call `planTodoExecution` with the `jobId` and array of tool names
   - Execute each tool in the planned sequence:
     - Use external tools as needed (web search, file operations, calculations, etc.)
     - After each tool execution, call `reportExecution` with `jobId`, tool name, and result
   - When all tools for the todo are complete, call `completeTodo` with `jobId` and `todoId`

4. **Completion**
   - When `selectNextTodo` returns `nextAction: 'finishJob'`, call `finishJob` with the `jobId`
   - This generates a comprehensive final report with all accumulated results

**Critical Rules:**
- ALWAYS follow the `nextAction` field in responses to know what to do next
- NEVER skip steps or change the protocol order
- Track the full `context` to understand current workflow state
- Report ALL tool executions with their actual results
- When `nextAction` is null, the workflow is complete

**Example Workflow:**
User: "Research competitors and create a market analysis report"

1. startJob(goal: "Research competitors a

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategoryAutomation
Updated1y ago
Forks0

Languages

Monkey C

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low