MCP Architector
Related Servers
Alternatives to MCP Architector
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA local-first MCP server providing secure workspace file operations, offline full-text search, and web search/fetch capabilities without requiring API keys.10-
- AlicenseBqualityCmaintenanceA local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.7447 npm6MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server providing persistent memory for AI coding assistants by storing and searching architectural decisions, patterns, and solutions. It also includes tools for git automation and mapping codebase expertise based on project history.MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that lets AI assistants search and retrieve context from indexed projects, Git state, decisions, and tasks without sending data to the cloud.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.32MIT
- FlicenseBqualityCmaintenanceA fully local, privacy-first MCP server that gives AI coding assistants deep repository intelligence with file-and-line-cited answers, persistent semantic memory, and agentic abilities like task planning and code review—all without any cloud API calls.23-
TDQS
Scored across 28 tools
Tools are well-described with distinct purposes, but the large number of entry manipulation tools (set-entry, set-entries, replace-entries, import-entries, delete-entry, delete-entries) could lead to confusion. However, descriptions clearly specify when to use each, making disambiguation possible with careful reading.
All tools use a consistent verb_noun pattern in snake_case (e.g., list-entries, set-module-details, delete-slice). Related operations share prefixes (set-*, delete-*, list-*, get-*, validate-*), making the API predictable and easy to navigate.
With 28 tools, the count is high but justified by the complexity of the domain (managing entries, modules, slices, projects, imports, validation, and bulk operations). Some redundancy (e.g., import-entries as alias for replace-entries) could be trimmed, but overall the tool set is well-scoped for a comprehensive architecture management server.
The tool set covers all essential operations: CRUD for entries, modules, slices, and projects; listing, searching, validation, bulk imports, data flow management, and refactoring. No obvious gaps are apparent; even edge cases like index drift and slice definition are addressed.