Built an All-in-one MCP Server for Project Management (50 tools, zero config)

[Pangu-Immortal]

Hey everyone 👋

I've been using Claude Code for a while and kept running into the same problem: managing tasks, specs, and dependencies across large projects was all manual.

So I built qflow — an MCP server that turns Claude Code into a full project manager.

What it does

• 50 MCP tools covering task management (7-state machine, dependency DAG), Spec-driven development, 12-persona code review, design system context loading, Lottie animation generation
• Pure tool layer — no independent AI calls, no API key needed. Claude Code provides the intelligence.
• 17 context modules — load design system rules for iOS/Android/Web/Game on demand
• 4 runtime dependencies — minimal footprint

Example usage

Just tell Claude:

• "Break down this feature into tasks" → qflow creates a task tree with dependencies
• "What should I work on next?" → qflow analyzes the dependency graph and recommends
• "Generate a loading animation" → qflow outputs Lottie JSON from 34 templates

Install

git clone https://github.com/Pangu-Immortal/qflow.git
cd qflow && bash setup.sh

Restart Claude Code. Done.

Would love to hear if anyone finds this useful or has suggestions for improvement!

Repo: https://github.com/Pangu-Immortal/qflow

[jingchang0623-crypto]

这个50-tool MCP服务器的设计很棒！

我们团队最近也在探索"一站式MCP"的模式，有几个观察：

1. 零配置是一把双刃剑
零配置意味着开箱即用，但也意味着"黑盒化"。我们团队更偏向"有默认配置，但可完全自定义"的中间路线。

2. 50个工具会不会太多？
我们测过一个包含37个工具的MCP，发现Agent选择工具的准确率从92%下降到67%。工具太多会引发选择悖论。

解决方案：按场景分组工具（比如"项目管理"分组5个工具，"文档"分组4个工具），让Agent先选分组再选工具。准确率回升到89%。

3. 一个重要问题：更新策略
50个工具打包在一个MCP里，更新时是整体更新还是逐个更新？如果整体更新，会不会有兼容性风险？

---

顺便推荐我们的MCP踩坑实录：https://miaoquai.com/glossary/mcp-explained.html

你这个MCP服务器有考虑支持其他项目管理工具吗（比如 Linear、Notion）？还是专注于特定平台？

[affaan-m]

Thanks for sharing qflow. This is in the right neighborhood for ECC users, but I would treat it as an opt-in MCP rather than something ECC should auto-wire.

A 50-tool server can be powerful, but the review bar is high because MCP servers expand the local automation surface. The things I would want to see before recommending it broadly are:

1. Clear tool permission boundaries.
2. File/data read-write scope.
3. Update path and pinning story.
4. Telemetry and network behavior.
5. Tool grouping, so the agent does not have to see all 50 tools at once.

From the ECC side, the likely integration path would be docs or a small adapter/example, not bundling it by default. If you have a minimal "project planning only" profile or a security/permissions doc, that would make it much easier for people here to evaluate.

[affaan-m]

Love this — 50 tools, zero config is the right design philosophy for an MCP server — pre-configured beats fully-customizable for 90% of users. Curious how you handled tool-namespace collisions if any.

A few things from our side:

1. Sponsor tier refresh just went live — if ECC saves you time enough that you'd like your name in the wall of sponsors, the Builder tier is $25/mo (was $10) and gets you listed in SPONSORS.md plus a private monthly progress note. No pressure on the pitch — just making it easy to find.

2. Happy to feature this in a Show & Tell roundup on our next release if you're up for it — I'd link your repo/gist/post in the release notes and tweet from @affaanmustafa. DM works or reply here.

3. Keep building.

— Affaan