capture_rate_report — entsoe-mcp MCP Prompt

capture_rate_report is one of 3 prompts on the entsoe-mcp MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke capture_rate_report from your client

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

Other prompts on this server

• zone_briefing
• battery_spread_scan

entsoe-mcp also offers 4 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.