fcop-mcp
Related Servers
Alternatives to fcop-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that combines Read+Edit file operations into single tool calls. 80-95% fewer tool calls formulti-file refactoring across Claude, Cursor, Windsurf, and more.323 npm3MIT
- FlicenseNot gradedqualityDmaintenanceA multi-tool task agent MCP server with file search, SQLite query, calculator, and report writing tools. Enables Claude Code, Claude Desktop, or Cursor to control the same tools used by the agent, with guardrails for safety.-
- AlicenseNot gradedqualityBmaintenanceProvides 300+ MCP tools for orchestrating AI agents — including swarm coordination, self-learning memory, and task management — enabling MCP clients like Claude Code and Cursor to spawn, coordinate, and learn from specialist agents across sessions.21,506 npm1MIT
- AlicenseNot gradedqualityAmaintenanceExposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.MIT
- AlicenseAqualityAmaintenanceLocal-first shared memory and task coordination for AI coding agents. One Go binary, MCP server, markdown files you own. Hooks for Claude Code and Codex CLI (and their desktop apps).305MIT
- AlicenseAqualityDmaintenanceAn agent orchestration layer that wraps expert agents as MCP tools, enabling integration with Claude Desktop, Cursor, and other MCP-compatible environments.411 npm9MIT
TDQS
Scored across 45 tools
Several tools have unclear boundaries: write_task and create_task are explicitly functionally identical, and fcop_check, fcop_audit, list_governance_events, and fcop_list_alerts all overlap as audit/governance surfaces. The lifecycle transitions are distinct, but the duplicate task creator and the cluster of similar check/audit tools will cause misselection.
Most tools follow a readable lowercase snake_case verb_noun style, but the conventions are mixed: creation verbs vary across init_, create_, write_, and new_, and the fcop_ prefix is applied only to some admin tools while others like redeploy_rules and check_update lack it. The naming is still navigable but not consistent enough to be predictable.
45 tools is far beyond the 25-tool threshold for a well-scoped server, and many are conveniences or near-duplicates such as create_task/write_task and bulk_archive_to_history. The broad FCoP lifecycle partially justifies the size, but the surface is overgrown and should be consolidated.
The core lifecycle is well covered: initialization, task creation and state transitions, reports, reviews, history archiving, workspaces, and governance alerts. However, issues have no read or update tool, and tasks/reports lack edit or delete operations, leaving notable gaps for a project-management domain.