boris-mcp
Related Servers
Alternatives to boris-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that reads a team's interviews, tickets, and docs to build a model of the product, exposing tools to ask questions, list contradictions and gaps, and draft documents, with all answers citing their source fragments.610 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding agents structured access to a project's architecture, rules, modules, and technical decisions.MIT
- AlicenseAqualityAmaintenanceMCP server exposing memory search, index, and stats tools for agents, with honesty guards to prevent re-litigation of settled decisions.577 PyPI6AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceLiminal turns objectives into structured work by strategizing through an atomic, deterministic basis: setting guardrails around scope, compiling resources and constraints, uncovering gaps, and organizing research and next steps. All while carrying continuity and priorities forward so your AI builds on what’s already done.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides CLI coding agents with persistent decision memory, codebase dependency-graph awareness, plan validation against architectural constraints, and a self-bootstrapping constraints.md file.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives your agent a persistent project brain: vision, architecture decisions, conventions, roadmaps, and automatic session handoff.9 npm7MIT
TDQS
Scored across 17 tools
Each tool targets a distinct resource or action: informational (guide, about, whoami), knowledge (projects, design_decisions, doctrine), messaging (send_message, my_messages, inbox, reply), and administration (access_requests, grant, revoke, activity). No two tools have overlapping purposes.
All tool names follow a consistent pattern of lowercase snake_case, with single words or underscore concatenations (e.g., design_decisions, send_message, access_requests). No mixing of conventions like camelCase or PascalCase.
17 tools is slightly above the typical well-scoped range (3-15), but each tool covers a necessary function for the server's stated purpose (personal knowledge, updates, messaging, access control). The count feels justified given the comprehensive scope.
The tool set covers all apparent use cases: getting to know Boris (guide, about, projects, design_decisions, doctrine, stack), staying updated (whats_new), communicating (send_message, my_messages, inbox, reply), and managing access (access_requests, activity, grant, revoke). No critical gaps are present.