how_to_get_my_usage — ElectricityFinder MCP Tool
how_to_get_my_usage
(how to get my usage) is one of 3 tools on the
ElectricityFinder
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call how_to_get_my_usage from your client
- Claude Code ElectricityFinder how_to_get_my_usage run in your project directory
- Claude Desktop ElectricityFinder how_to_get_my_usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ElectricityFinder how_to_get_my_usage ~/.cursor/mcp.json
- VS Code ElectricityFinder how_to_get_my_usage .vscode/mcp.json
- Zed ElectricityFinder how_to_get_my_usage ~/.config/zed/settings.json
- Windsurf ElectricityFinder how_to_get_my_usage ~/.codeium/windsurf/mcp_config.json
- Cline ElectricityFinder how_to_get_my_usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ElectricityFinder how_to_get_my_usage ~/.gemini/settings.json
- Grok ElectricityFinder how_to_get_my_usage .mcp.json (in your project root)
- ChatGPT ElectricityFinder how_to_get_my_usage Settings → Connectors → Advanced → Developer mode
- Claude.ai ElectricityFinder how_to_get_my_usage Settings → Connectors → Add custom connector
- LangChain ElectricityFinder how_to_get_my_usage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http electricityfinder https://electricityfinder.online/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.