TaskFlow MCP 🔄✅

Created By
pinkpixel-deva year ago
A task management Model Context Protocol (MCP) server that helps AI assistants break down user requests into manageable tasks with subtasks, dependencies, and notes. Enforces a structured workflow with user approval steps.
Overview

what is TaskFlow MCP?

TaskFlow MCP is a task management Model Context Protocol (MCP) server designed to assist AI assistants in planning and executing tasks by breaking down user requests into manageable components.

how to use TaskFlow MCP?

To use TaskFlow MCP, install it globally or locally via npm, start the server, and configure your MCP client to connect to it. You can then plan tasks, track progress, and manage approvals through various commands.

key features of TaskFlow MCP?

  • Task Planning: Break down complex requests into manageable tasks.
  • Subtasks: Divide tasks into smaller, manageable subtasks.
  • Progress Tracking: Visualize task status and progress.
  • User Approval: Enforce approval steps for quality control.
  • Persistence: Save tasks for continuity across sessions.
  • Export Options: Export task plans in various formats.

use cases of TaskFlow MCP?

  1. Managing project tasks for AI-driven applications.
  2. Coordinating team workflows with user approval processes.
  3. Tracking progress of complex user requests in AI systems.

FAQ from TaskFlow MCP?

  • Can TaskFlow MCP handle multiple requests simultaneously?

Yes! It is designed to manage multiple tasks and requests efficiently.

  • Is TaskFlow MCP free to use?

Yes! TaskFlow MCP is open-source and free to use under the MIT License.

  • How can I contribute to TaskFlow MCP?

Contributions are welcome! Please refer to the contributing guidelines in the repository.

Server Config

{
  "mcpServers": {
    "taskflow": {
      "command": "npx",
      "args": [
        "-y",
        "@pinkpixel/taskflow-mcp"
      ],
      "env": {
        "TASK_MANAGER_FILE_PATH": "/path/to/tasks.json"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pinkpixel-dev
Star
11
Language
JavaScript
License
MIT license
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago