energy_expert — OrbitEOS Energy Management MCP Prompt

energy_expert is one of 2 prompts on the OrbitEOS Energy Management MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke energy_expert from your client

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

Other prompts on this server

• electrician_mode

OrbitEOS Energy Management also offers 3 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.