DriftOS MCP Server
OfficialRelated Servers
Alternatives to DriftOS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables routing tasks to the right specialist agents, assembling the needed context from a layered catalog of agents, skills, knowledge, runbooks, topics, tools, and connectors, while remembering how a business wants work done.1020 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI systems to remember interactions, understand document context through semantic search, and intelligently route requests with persistent memory and quality-scored content synthesis.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables intelligent conversation management with 4 AI agents that provide semantic analysis, pattern discovery, automatic documentation, and relationship mapping. Logs and analyzes Claude conversations with 70% token optimization and multi-language support.2-
- AlicenseNot gradedqualityBmaintenanceEnables product discovery, session-scoped carts, and confirmation-gated checkout through natural language, with deterministic routing and safety features.3 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered multi-provider routing and chat through an MCP interface, with smart fallback, persistent sessions, and learning from historical performance.1 npm4MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to turn an uncertain routing decision into a confidence-scored choice among explicit routes, with a thresholded recommendation to proceed, review deeper, or ask for human input, while remaining advisory-only.1MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: route_message handles message routing, list_branches lists branches, get_context assembles context, build_prompt constructs prompts, get_facts retrieves facts, and extract_facts triggers fact extraction. The descriptions clearly differentiate their functions, making tool selection unambiguous.
All tools follow a consistent verb_noun naming pattern with the 'driftos_' prefix (e.g., driftos_route_message, driftos_list_branches). The structure is uniform throughout, using snake_case consistently without any deviations or mixed conventions.
With 6 tools, this server is well-scoped for managing conversation branches, context, and facts in a drift detection system. Each tool serves a specific, necessary function (routing, listing, context assembly, prompt building, fact retrieval, and fact extraction), and none feel redundant or missing for the domain.
The tool set provides complete coverage for the conversation drift management domain: routing messages, listing branches, getting context, building prompts, and handling facts (both retrieval and extraction). There are no obvious gaps; agents can perform all core operations from routing to LLM integration without dead ends.