journey_material — Warmth Engine Observatory MCP Prompt

journey_material is one of 3 prompts on the Warmth Engine Observatory MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke journey_material from your client

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

Other prompts on this server

• journey_coordination
• journey_stack

Warmth Engine Observatory also offers 1 resource — 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.