build_onboarding_link — Vivid MCP MCP Tool
build_onboarding_link
(build onboarding link) is one of 1 tool on the
Vivid MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call build_onboarding_link from your client
- Claude Code Vivid MCP build_onboarding_link run in your project directory
- Claude Desktop Vivid MCP build_onboarding_link ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vivid MCP build_onboarding_link ~/.cursor/mcp.json
- VS Code Vivid MCP build_onboarding_link .vscode/mcp.json
- Zed Vivid MCP build_onboarding_link ~/.config/zed/settings.json
- Windsurf Vivid MCP build_onboarding_link ~/.codeium/windsurf/mcp_config.json
- Cline Vivid MCP build_onboarding_link ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vivid MCP build_onboarding_link ~/.gemini/settings.json
- Grok Vivid MCP build_onboarding_link .mcp.json (in your project root)
- ChatGPT Vivid MCP build_onboarding_link Settings → Connectors → Advanced → Developer mode
- Claude.ai Vivid MCP build_onboarding_link Settings → Connectors → Add custom connector
- LangChain Vivid MCP build_onboarding_link pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vivid-mcp https://api.prime.vivid.money/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.