_endpoints — entsoe-mcp MCP Resource

_endpoints is one of 4 resources on the entsoe-mcp MCP server. Connect the server and your client can attach it as context.

by client

How to attach _endpoints from your client

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

Other resources on this server

• _zones
• _psr_types
• _coverage

entsoe-mcp also offers 3 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, 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 resource's type and contents.