claude-faf-mcp and coolify-mcp
Both are MCP servers, making them competitors, as they offer alternative implementations for managing different PaaS solutions and services, though they target different ecosystems (Coolify vs. .faf).
About claude-faf-mcp
Wolfe-Jam/claude-faf-mcp
Anthropic MCP server for .faf — 33 tools, IANA-registered format. npm: claude-faf-mcp. MCP Registry #2759
Provides 33 MCP tools for creating and managing `.faf` files—a YAML format that captures project context (who it's for, what it does, why it exists) to optimize AI understanding across sessions. Features bi-directional and tri-directional sync with `CLAUDE.md` and `MEMORY.md`, auto-detection of project stacks, AI-readiness scoring (0-100%), and interoperability with other LLM platforms (Gemini, Grok, Cursor) through a shared `.faf` specification. Runs entirely locally with zero dependencies, averaging 19ms per tool execution, and uses stdio transport for Claude Desktop integration.
About coolify-mcp
StuMason/coolify-mcp
MCP server for Coolify — 38 optimized tools for managing self-hosted PaaS through AI assistants
This tool helps developers and operations engineers manage their self-hosted applications, databases, and services running on Coolify using natural language. It takes your spoken or written commands, translates them into actions, and provides concise summaries of your infrastructure. This allows you to debug issues, deploy new features, or perform bulk operations simply by asking an AI assistant.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work