nucleus_wakeup_wait — nucleus MCP Tool
nucleus_wakeup_wait
(nucleus wakeup wait) is one of 28 tools on the
nucleus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call nucleus_wakeup_wait from your client
- Claude Code nucleus nucleus_wakeup_wait run in your project directory
- Claude Desktop nucleus nucleus_wakeup_wait ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor nucleus nucleus_wakeup_wait ~/.cursor/mcp.json
- VS Code nucleus nucleus_wakeup_wait .vscode/mcp.json
- Zed nucleus nucleus_wakeup_wait ~/.config/zed/settings.json
- Windsurf nucleus nucleus_wakeup_wait ~/.codeium/windsurf/mcp_config.json
- Cline nucleus nucleus_wakeup_wait ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI nucleus nucleus_wakeup_wait ~/.gemini/settings.json
- Grok nucleus nucleus_wakeup_wait .mcp.json (in your project root)
- ChatGPT nucleus nucleus_wakeup_wait Settings → Connectors → Advanced → Developer mode
- Claude.ai nucleus nucleus_wakeup_wait Settings → Connectors → Add custom connector
- LangChain nucleus nucleus_wakeup_wait pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nucleus https://relay.nucleusos.dev/mcpOther tools on this server
- nucleus_governance
- nucleus_features
- nucleus_sessions
- nucleus_tasks
- nucleus_sync
- nucleus_next_message
- nucleus_relay_subscribe
- nucleus_ccr_arm
- nucleus_orchestration
- nucleus_telemetry
- nucleus_slots
- nucleus_infra
- nucleus_agents
- nucleus_federation
- nucleus_engrams
- nucleus_relay
- nucleus_route
- nucleus_audit
- nucleus_delegate
- nucleus_lane_init
- nucleus_lane_start
- nucleus_lane_stop
- nucleus_lane_status
- nucleus_lane_feedback
- nucleus_plan_execute
- nucleus_plan_import
- nucleus_plan_list
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.