Onboarding MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_vault_pathB | Set the active Obsidian vault directory path for the session state. |
| set_workspace_pathA | Set the active workspace directory path for the session state. |
| get_codebase_structureA | Recursively scan workspace directory and return file tree and dependencies, respecting .gitignore. |
| process_videoA | Process onboarding video: extract audio, transcribe with Whisper, extract scene keyframes, and return timestamp-aligned JSON payload. |
| write_obsidian_noteC | Write a markdown note into the active Obsidian vault directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.