INDIVIDUAL MCP TOOL
demand_share_multiple
How much of the area's demand does this one site take, said as a multiple of the mean station?
LIVE ENDPOINT
https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp
Connect to this endpoint to inspect the live schema for demand_share_multiple and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tern-mcp]
url = "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tern-mcp": {
"type": "http",
"url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tern-mcp
Remote MCP URL: https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tern-mcp": {
"url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tern-mcp": {
"type": "http",
"url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tern-mcp",
"transport": "streamable-http",
"url": "https://tern-mcp-dev-537572042041.europe-west4.run.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
search_charging_stations— Find charging stations in one country by structured filter — id, title, address, operator.nearby_charging_stations— List the charging stations within a radius of a point, nearest first.list_evses— List the individual EVSEs (connectors) of up to 20 stations, with their capacity in kW.aggregate_charging_utilization— Station-level utilization aggregated over a GeoJSON area and a date window of at most 92 days, optionally filtered to a capacity band (default 150 kW = HPC; pass 100 for fast charging).aggregate_evse_utilization— EVSE-level utilization aggregated over a GeoJSON area and a date window of at most 92 days, optionally filtered to a capacity band.area_benchmark— How hard is each EVSE at this site working compared with the area around it?avg_session_minutes— How long does a session at this site actually last?busy_evse_hours— How many EVSE-hours at this station carried charging on the drilled day, and how many of its EVSEs were charging at once in the busiest hour?