resource_training — nucleus MCP Resource

resource_training is one of 19 resources on the nucleus MCP server. Connect the server and your client can attach it as context.

by client

How to attach resource_training from your client

• Claude Code nucleus Resource/resource_training run in your project directory
• Claude Desktop nucleus Resource/resource_training ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor nucleus Resource/resource_training ~/.cursor/mcp.json
• VS Code nucleus Resource/resource_training .vscode/mcp.json
• Zed nucleus Resource/resource_training ~/.config/zed/settings.json
• Windsurf nucleus Resource/resource_training ~/.codeium/windsurf/mcp_config.json
• Cline nucleus Resource/resource_training ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI nucleus Resource/resource_training ~/.gemini/settings.json
• Grok nucleus Resource/resource_training .mcp.json (in your project root)
• ChatGPT nucleus Resource/resource_training Settings → Connectors → Advanced → Developer mode
• Claude.ai nucleus Resource/resource_training Settings → Connectors → Add custom connector
• LangChain nucleus Resource/resource_training pip install langchain-mcp-adapters

Other resources on this server

• resource_state
• resource_events
• resource_triggers
• resource_depth
• resource_context
• resource_changes
• resource_traces
• resource_health
• resource_cycle
• resource_arc
• resource_deltas
• resource_frontiers
• resource_growth
• resource_flywheel_csr
• resource_flywheel_dashboard
• resource_flywheel_thesis
• resource_flywheel_mentor
• resource_flywheel_week

nucleus also offers 8 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.