Onboarding MCP Server
Related Servers
Alternatives to Onboarding MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA local MCP server that gives AI agents structured access to a personal Obsidian knowledge vault, with semantic search, organization through Maps of Content, and git-backed history.-

Vibgrate AI Contextofficial
AlicenseNot gradedqualityBmaintenanceLocal-first MCP server that gives AI assistants codebase intelligence—code graph, drift analysis, vulnerability attribution, and version-correct library docs—all from the user's machine.1,569 npm4Apache 2.0- AlicenseNot gradedqualityAmaintenanceA local-first MCP server that gives AI coding agents durable project memory, dependency graphs, and impact analysis to answer team knowledge and cross-file change questions before editing.28 npm1-
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3760 npm6MIT
- AlicenseAqualityAmaintenanceA local-first MCP server that gives AI coding agents persistent memory and controlled commands. Features a git-backed markdown knowledge vault with FTS5 search, surgical section edits, token-aware context budgeting, and a sandboxed command engine with human approval gates. Works with Claude Code, Cursor, Copilot, Gemini, and more.458316 npm1Apache 2.0
- 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.747 npm6MIT
TDQS
Scored across 5 tools
Tools are mostly distinct, but set_vault_path and set_workspace_path have near-identical names and purposes, differing only by target directory. The other three tools (get_codebase_structure, process_video, write_obsidian_note) are clearly distinct actions.
All tool names follow a consistent verb_noun pattern: set, set, get, process, write. The nouns are descriptive and uniform in style, making the API predictable.
Five tools are well-scoped for an onboarding workflow, covering path setup, codebase analysis, video processing, and note writing without unnecessary bloat.
The toolset covers the core onboarding steps, but there are minor gaps such as no tool to list or manage existing notes, and no way to inspect the video metadata before processing. These are workable but not exhaustive.