mcp-executor

Execute multi-tool MCP workflows with retry logic and progress updates.

1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/mcfearsome/cc-colony --skill mcp-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-executor
Source: https://github.com/mcfearsome/cc-colony/tree/main/.claude/skills/mcp-executor
Command: npx skills add https://github.com/mcfearsome/cc-colony --skill mcp-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Traditional AI agent setups often suffer from "token bloat" when every agent loads extensive tool schemas. This Skill solves that by centralizing complex multi-tool operations within a dedicated executor agent, drastically reducing token usage across your AI colony and simplifying the orchestration of sophisticated workflows.

Core Features & Use Cases

  • Token-Efficient Multi-Tool Workflows: Execute complex sequences of Model Context Protocol (MCP) tool calls (e.g., fetch data, transform, validate, store) using TypeScript or Python, without burdening other agents with large tool schemas.
  • Parallel & Resilient Execution: Perform multiple independent operations concurrently and implement robust error recovery with retry logic and fallbacks.
  • Centralized MCP Expertise: Delegate advanced data processing, file system interactions, and database operations to a specialist agent.
  • Use Case: An agent needs to query a database, process the results, write them to a file, and then commit the file to Git. Instead of handling all MCP schemas and logic itself, it sends a single request to the mcp-executor agent, which performs the entire workflow efficiently and cost-effectively.

Quick Start

To request a task from the MCP Executor agent, send it a message detailing the workflow. For example, ask it to "Execute MCP workflow: Fetch user data from database and generate report" specifying the pattern (e.g., multi-tool-workflow), the language (TypeScript or Python), and the MCP tools required, such as mcp__database__query and mcp__filesystem__writeFile. The executor will handle the execution and return the results via message.

Frequently Asked Questions about mcp-executor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage when orchestrating multiple MCP tool calls across agents?

Centralize multi-tool workflows in a dedicated executor agent. Instead of loading all tool schemas into every agent, delegate complex sequences—like database queries, file writes, and Git commits—to a specialist that handles MCP calls efficiently, cutting token bloat across your colony.

Can I run parallel MCP workflows with retry logic and error recovery?

Yes. The executor agent performs multiple independent MCP operations concurrently, implements robust retry logic and fallbacks, and returns results with progress updates, enabling resilient multi-tool pipelines without manual error handling in your main agents.

What languages and execution environments does the MCP executor support?

The executor runs TypeScript via Deno or Python, accesses local MCP servers through a local MCP client, and executes workflows via Bash. It integrates with colony-based environments where non-MCP agents request complex multi-tool scenarios.

How do I request a workflow from the MCP executor agent?

Send the executor a message describing the workflow pattern (e.g., multi-tool-workflow), specify the language (TypeScript or Python), list required MCP tools (e.g., mcp__database__query, mcp__filesystem__writeFile), and it composes and executes the calls, returning results via colony messages.

Is the MCP executor suitable for scenarios requiring 3+ sequential tool calls and data transformation?

Yes. It's designed for multi-tool pipelines (3+ MCP calls), data transformation tasks, and complex workflows. It eliminates the need for individual agents to manage schemas and orchestration logic for sophisticated sequences.

What types of operations can the executor handle beyond simple tool calls?

Beyond single calls, it handles parallel processing of independent operations, retry mechanisms with fallbacks, multi-step data transformations, and end-to-end workflows combining database queries, file system interactions, and external tool invocations.