complete_onboarding_step — Aeroz MCP Tool
complete_onboarding_step
(complete onboarding step) is one of 30 tools on the
Aeroz
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call complete_onboarding_step from your client
- Claude Code Aeroz complete_onboarding_step run in your project directory
- Claude Desktop Aeroz complete_onboarding_step ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aeroz complete_onboarding_step ~/.cursor/mcp.json
- VS Code Aeroz complete_onboarding_step .vscode/mcp.json
- Zed Aeroz complete_onboarding_step ~/.config/zed/settings.json
- Windsurf Aeroz complete_onboarding_step ~/.codeium/windsurf/mcp_config.json
- Cline Aeroz complete_onboarding_step ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aeroz complete_onboarding_step ~/.gemini/settings.json
- Grok Aeroz complete_onboarding_step .mcp.json (in your project root)
- ChatGPT Aeroz complete_onboarding_step Settings → Connectors → Advanced → Developer mode
- Claude.ai Aeroz complete_onboarding_step Settings → Connectors → Add custom connector
- LangChain Aeroz complete_onboarding_step pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aeroz https://api.aeroz.io/mcp
Other tools on this server
- verify_chip
- check_recall
- dpp_readiness
- list_findings
- list_agents
- get_usage
- list_sandbox_chips
- onboarding_status
- onboarding_next_step
- business_brief
- ask_agent
- agent_conversation
- create_shipment
- shipment_status
- list_shipments
- log_telemetry
- record_custody
- plan_route
- shipment_profiles
- bind_graded_item
- graded_item
- record_provenance
- list_graded_items
- my_section
- trace_unit
- find_unit
- chain_readiness
- get_passport
- verify_passport_credential
This list was read from the server itself, by connecting to it and calling tools/list on 15 October 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.