A
licenseA
qualityA
maintenanceMCP server that enables running and managing file-based AI Skills, Agents, and Flow workflows as DAGs, with tools for listing, executing, and resuming tasks via stdio JSON-RPC.
9
MIT
AIMFP
by aryanduntley
Related Servers
Alternatives to AIMFP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.9 npm2MIT
- AlicenseCqualityAmaintenanceAn MCP server implementing Spec-Driven Development workflows for AI-agent CLIs and IDEs like Claude Code and Cursor, enabling spec-first development with automated workflow guidance and quality checks.1678 npm51MIT
- AlicenseNot gradedqualityCmaintenanceA filesystem-backed MCP server with REST API for AI tool integration and project workflow tracking. Zero database required.205 npmMIT
- AlicenseBqualityAmaintenanceMCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.876Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides an AI LLM orchestrator supporting multiple providers (LM Studio, Ollama, OpenAI, generic) plus SQLite-backed memory, kanban, and todo databases for persistent task and knowledge management.-
TDQS
B3/5.0
Scored across 253 tools
Disambiguation3/5
Many tools have similar purposes (e.g., various add and get functions for items, tasks, subtasks, sidequests) and the large number creates potential confusion. However, detailed descriptions help distinguish them, and each tool has a specific role.
Naming Consistency5/5
Tool names consistently follow a verb_noun pattern (e.g., add_item, get_task, delete_file, update_module). Even orchestrators like aimfp_init and get_git_status follow a recognizable naming convention. No mixing of styles.
Tool Count1/5
With 253 tools, the server is extremely large for an MCP server. Most well-designed servers have under 20 tools. This count suggests over-engineering and would overwhelm any agent attempting to choose the right tool.
Completeness5/5
The tool set covers an exhaustive set of operations for the domain: CRUD, batch operations, search, state management, initialization, and orchestration. There are no obvious gaps for the tracked entities (files, functions, types, modules, tasks, directives, etc.).
Maintenance
ActivitySlowing
ResponsivenessNo issues