fushiguro-mcp
Related Servers
Alternatives to fushiguro-mcp
No user-submitted related servers found.
Related Servers
FlicenseAqualityDmaintenanceEnables intelligent semantic conversation routing that automatically branches, maintains, and routes between conversation topics instead of relying on entire conversation histories for context.62-- AlicenseAqualityBmaintenanceEnables AI agents to manage, search, plan, and execute reusable skills while automatically enforcing always-on coding and reasoning guidelines. It provides workflow orchestration, permission-controlled execution, dynamic skill registration, and feedback-based ranking.924 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to autonomously manage and improve execution processes for repetitive task types by storing reusable task contexts with associated artifacts (practices, rules, prompts, learnings) and providing full-text search across historical best practices.81MIT
- AlicenseNot gradedqualityDmaintenanceEnables step-level routing of AI workflows by decomposing tasks, selecting the best model per step within constraints, executing steps, and providing full execution traces.1Apache 2.0
- AlicenseCqualityDmaintenanceIntelligent routing layer that analyzes tasks and guides your AI agent to delegate work to specialized tools (Gemini, Aider, Copilot) using rule-based and capability-based routing.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables enterprise AI agents to discover and invoke MCP tools, resources, and prompts across GitHub, ITSM, and business systems through a policy-controlled gateway with human approval and auditability.MIT
TDQS
Scored across 10 tools
Each tool targets a distinct phase or store: planning, stage prompts, catalog browsing, memory CRUD, knowledge search, router feedback, and status. The only mild ambiguity is between recall (personal preferences) and search_knowledge (organizational docs), but the descriptions clearly separate the two corpora.
Tool names are all lowercase and mostly follow an imperative verb style, with clear verb_noun names like get_stage, list_catalog, and record_outcome. Minor deviations like bare 'brief' and the noun 'status' break the pattern slightly but remain readable and predictable.
10 tools is a well-scoped size for an orchestration and memory server; each tool earns its place by covering a distinct concern without redundancy. The count feels intentional rather than bloated or thin.
The surface covers planning, staged execution, catalog lookup, preference memory, knowledge retrieval, and router feedback, so core workflows are supported. Minor gaps exist: catalog and knowledge are read-only, and there is no explicit way to list or cancel active plans.