onboard_a_hire — onboarding MCP Prompt
onboard_a_hire
is one of 2 prompts on the
onboarding
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke onboard_a_hire from your client
- Claude Code onboarding Prompt/onboard_a_hire run in your project directory
- Claude Desktop onboarding Prompt/onboard_a_hire ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor onboarding Prompt/onboard_a_hire ~/.cursor/mcp.json
- VS Code onboarding Prompt/onboard_a_hire .vscode/mcp.json
- Zed onboarding Prompt/onboard_a_hire ~/.config/zed/settings.json
- Windsurf onboarding Prompt/onboard_a_hire ~/.codeium/windsurf/mcp_config.json
- Cline onboarding Prompt/onboard_a_hire ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI onboarding Prompt/onboard_a_hire ~/.gemini/settings.json
- Grok onboarding Prompt/onboard_a_hire .mcp.json (in your project root)
- ChatGPT onboarding Prompt/onboard_a_hire Settings → Connectors → Advanced → Developer mode
- Claude.ai onboarding Prompt/onboard_a_hire Settings → Connectors → Add custom connector
- LangChain onboarding Prompt/onboard_a_hire pip install langchain-mcp-adapters
Other prompts on this server
onboarding also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.