start_sprint — nucleus MCP Prompt

start_sprint is one of 8 prompts on the nucleus MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke start_sprint from your client

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

Other prompts on this server

• activate_synthesizer
• cold_start
• compound_context
• align_review
• weekly_synthesis
• flywheel_check
• flywheel_brief

nucleus also offers 19 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.