compound_context — nucleus MCP Prompt

compound_context 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 compound_context from your client

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

Other prompts on this server

• activate_synthesizer
• start_sprint
• cold_start
• 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.