{"id":"pinkpixel-dev-taskflow-mcp","name":"taskflow-mcp","homepage":null,"repo_url":"https://github.com/pinkpixel-dev/taskflow-mcp","category":"devtools","subcategories":[],"tags":["mcp","task-management","workflow","planning","typescript","yaml","persistence","export","archiving"],"what_it_does":"TaskFlow MCP is a Model Context Protocol (MCP) server that helps an AI assistant plan and execute task workflows. It creates requests with tasks/subtasks (including dependencies and notes), persists them to disk (JSON/YAML), enforces an approval-centric workflow, supports exporting status reports, and includes an archive system for completed requests.","use_cases":["Plan multi-step work into tasks and subtasks for AI-assisted execution","Track progress across tasks/subtasks and persist state across sessions","Manage task dependencies and add contextual notes","Export task plans/status to Markdown/JSON/HTML for reporting","Archive completed requests and later restore them","Apply consistent LLM guidance via configurable global prompts/prefix/suffix"],"not_for":["Use as a secure multi-user task service without isolation (it is file-based per working directory/path)","Workflows requiring a remote API with fine-grained authorization/auditing","High-scale concurrent task editing without collision/locking considerations"],"best_when":"You want a local or per-project MCP tool that persistently manages task plans and guides an assistant through a structured task/approval loop.","avoid_when":"You need strong server-side access control, multi-tenant isolation, or guaranteed concurrency safety across many simultaneous users/processes.","alternatives":["Other MCP task/workflow servers (if available in your MCP client ecosystem)","Local task managers with REST/CLI integrations (e.g., generic workflow tools)","Building a custom MCP server backed by a database with proper auth and concurrency control"],"af_score":59.5,"security_score":24.8,"reliability_score":36.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:28:59.327508+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["None explicitly described (local MCP server started via CLI)"],"oauth":false,"scopes":false,"notes":"The README describes configuration via environment variables and local file paths; no user authentication/authorization model is documented for the MCP server."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source npm package; no usage-based pricing described."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":59.5,"security_score":24.8,"reliability_score":36.2,"mcp_server_quality":86.0,"documentation_accuracy":72.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":10.0,"scope_granularity":0.0,"dependency_hygiene":55.0,"secret_handling":70.0,"security_notes":"Security posture is primarily local-file based with no documented authentication or authorization. Risk mainly comes from file path manipulation and lack of isolation: the MCP server persists to disk at user-supplied paths. TLS, secret management practices beyond general Node conventions, and dependency vulnerability management are not documented in the provided materials.","uptime_documented":0.0,"version_stability":60.0,"breaking_changes_history":45.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency guarantees documented for tools such as mark_task_done/update/delete/export. Repeated calls could create duplicates or overwrite depending on implementation.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Because persistence is file-based (tasks.yaml/tasks-archive.*), multiple concurrent MCP clients pointing at the same file/path may overwrite each other.","Approval-oriented workflow implies the assistant should pause for user confirmation; if the client ignores this, tasks may be marked done prematurely.","Export operations write to an outputPath; ensure outputPath permissions/paths are correct to avoid failures.","Delete/update operations may permanently remove data from the active request; be sure to understand when archiving is required."]}}