area_benchmark — Tern EV-Charging Analytics MCP Tool
area_benchmark
(area benchmark) is one of 26 tools on the
Tern EV-Charging Analytics
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call area_benchmark from your client
- Claude Code Tern EV-Charging Analytics area_benchmark run in your project directory
- Claude Desktop Tern EV-Charging Analytics area_benchmark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tern EV-Charging Analytics area_benchmark ~/.cursor/mcp.json
- VS Code Tern EV-Charging Analytics area_benchmark .vscode/mcp.json
- Zed Tern EV-Charging Analytics area_benchmark ~/.config/zed/settings.json
- Windsurf Tern EV-Charging Analytics area_benchmark ~/.codeium/windsurf/mcp_config.json
- Cline Tern EV-Charging Analytics area_benchmark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tern EV-Charging Analytics area_benchmark ~/.gemini/settings.json
- Grok Tern EV-Charging Analytics area_benchmark .mcp.json (in your project root)
- ChatGPT Tern EV-Charging Analytics area_benchmark Settings → Connectors → Advanced → Developer mode
- Claude.ai Tern EV-Charging Analytics area_benchmark Settings → Connectors → Add custom connector
- LangChain Tern EV-Charging Analytics area_benchmark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http usetern https://tern-mcp-537572042041.europe-west4.run.app/mcpOther tools on this server
- search_charging_stations
- nearby_charging_stations
- list_evses
- aggregate_charging_utilization
- aggregate_evse_utilization
- avg_session_minutes
- busy_evse_hours
- corridor_benchmark
- corridor_comparison
- daily_spike
- day_vs_similar
- demand_share_multiple
- estate_coverage
- estate_monthly_series
- hourly_spike
- monthly_sessions_per_stall_day
- peak_hour_co_saturation
- poi_context
- rank_gap
- road_context
- sessions_per_stall_day
- site_profile
- site_ranking
- total_charging_minutes
- total_sessions
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.