lsp-onboard

name	lsp-onboard
description	First-session project onboarding. Explores the project structure, detects build system, test runner, entry points, and key architecture patterns. Produces a structured project profile the agent can reference throughout the session.
argument-hint	[workspace-root-path]
user-invocable	true
allowed-tools	mcp__lsp__start_lsp mcp__lsp__detect_lsp_servers mcp__lsp__list_symbols mcp__lsp__find_symbol mcp__lsp__blast_radius mcp__lsp__run_build mcp__lsp__run_tests mcp__lsp__get_diagnostics mcp__lsp__get_editing_context
license	MIT
compatibility	Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
metadata	{"required-capabilities":"documentSymbolProvider","optional-capabilities":"referencesProvider callHierarchyProvider"}

lsp-onboard

First-session project onboarding. Run this when connecting to a new project for the first time. Explores the codebase via LSP tools and produces a structured project profile: languages, build system, test runner, entry points, key types, and architecture patterns.

The profile helps the agent make better decisions throughout the session without re-exploring the same ground. Run once per project; skip on subsequent sessions unless the project structure has changed significantly.

When to Use

• First time working in a new codebase
• After major structural changes (new packages, build system migration)
• When the agent seems confused about project conventions

Do NOT run this on every session. It's a one-time exploration.

---

Step 1: Detect languages and servers

mcp__lsp__detect_lsp_servers({ "workspace_dir": "<root>" })

Record which languages are present and which servers are available. This tells you what the project is built with.

Step 2: Initialize and verify

mcp__lsp__start_lsp({ "root_dir": "<root>" })

Wait for initialization. Call list_symbols on one key file to verify the workspace is indexed.

Step 3: Identify entry points

Search for common entry point patterns:

mcp__lsp__find_symbol({ "query": "main" })
mcp__lsp__find_symbol({ "query": "Run" })
mcp__lsp__find_symbol({ "query": "Handler" })

Record entry points with their file paths. These are where execution starts.

Step 4: Map the package structure

For each top-level directory that contains source files, call list_symbols on one representative file:

mcp__lsp__list_symbols({ "file_path": "<dir>/main.go", "format": "outline" })

Build a mental map: which packages exist, what they export, how they relate. Cap at 10 packages to avoid spending too long.

Step 5: Detect build and test commands

mcp__lsp__run_build({ "workspace_dir": "<root>" })
mcp__lsp__run_tests({ "workspace_dir": "<root>" })

Record whether build and tests pass, and what language/toolchain was detected. Note the test count and any failures.

Step 6: Identify hotspots

Pick the 3-5 files that appear most central (entry points, shared types, core logic). For each:

mcp__lsp__blast_radius({ "changed_files": ["<file>"] })

Files with the most non-test callers are the architectural hotspots. Changes to these files have the widest blast radius.