Skip to main content

MCP Server

Module: None (platform) | Auth: OAuth 2.1 | Role: Any member | Licence: Free+

Eve is accessible as an MCP (Model Context Protocol) server, allowing Claude Code, Claude Desktop, and other MCP clients to use Eve's tools directly.

There are two MCP surfaces, each with its own audience and tool scope:

SurfaceEndpointAudienceToolsAuth
Workspace Evehttps://eve.ev.energy/mcpWorkspace members (B2B) — utility / fleet operators, analysts, engineersAll insight / insight:policy / operations:agents tools (filtered by enabled modules)OAuth 2.1
Driver Evehttps://eve.ev.energy/connect/mcpIndividual EV drivers (B2C)15-verb enrollment surface only — my_account, discover, connect_device, update_account, my_transactions, refer_friend, the card verbs (activate_charging_card, add_payment_card, update_card, remove_card), my_notifications, etc.ev.energy OAuth bearer (driver's own token)

The rest of this page documents Workspace Eve. For the driver-side surface, see Connect — driver-facing Eve.

Endpoint: https://eve.ev.energy/mcp

Connection Setup​

OAuth​

Add to your MCP client configuration:

{
"mcpServers": {
"eve": {
"url": "https://eve.ev.energy/mcp"
}
}
}

On first use, a browser window opens showing a provider selection page. Choose your sign-in provider (ev.energy, Google, or Microsoft) to authenticate. Tokens auto-refresh for 30 days.

Claude Code: Add to ~/.claude/settings.json or project .mcp.json. Claude.ai: Settings > Integrations > Add MCP Server.

Workspace API keys have been removed. OAuth with scoped keys for headless access is planned.

Tools by Module​

Tools are dynamically filtered based on your workspace's enabled modules:

ModuleExample ToolsDescription
insight (always on)create_scenario, add_evs_to_scenario, simulate_and_graph_scenario, analyze_load, show_region, query_hosting_capacity, get_platform_docSimulation, grid data, charts, docs
insight:policyask_policy_researcher, ask_policy_librarian, ask_policy_navigatorPolicy agent dispatch tools
operations:agentscreate_agent, update_agent, remove_agent, list_agents, create_skill, create_agent_teamAgent and skill management
programs:connectlist_campaigns, view_campaign_performance, create_campaign, update_campaign, create_contacts, launch_campaignPartner campaigns — tracked links, contacts, clicks, performance (verbs)
programs:affiliatelist_codes, create_code, update_codePartner codes — redemptions + qualified, no amounts (verbs)

Hosting Capacity Tools (with insight)​

  • query_hosting_capacity — Query grid capacity for a location
  • set_scenario_capacity_limit — Constrain simulation to grid capacity
  • analyze_hosting_capacity_constraints — Analyze capacity impact
  • calculate_hosting_capacity_deferral_benefit — Calculate deferral value

Resources​

Platform documentation is available as MCP resources:

resource://docs/simulations/overview
resource://docs/simulations/ev-charging
resource://docs/grid/hosting-capacity
resource://docs/agents/overview
...

Fetch any document on demand via the resource URI.

Authentication Scopes​

Auth MethodScopePrivate Agents
OAuth (browser SSO)PrivateYes — personal/restricted agents visible

Security​

  • All requests require an OAuth Bearer token
  • PKCE required for OAuth (S256 only)
  • Single-use authorization codes (5-minute TTL)
  • Token rotation on refresh (old token revoked atomically)
  • MCP access tokens are 60-minute JWTs; refresh tokens last 30 days

Client Compatibility​

ClientStatusNotes
Claude Code (CLI)Fully supportedAll tools, all operations
Claude Code (VS Code / JetBrains)Fully supportedSame as CLI
Claude.ai (web)SupportedTool calls work; long operations (>30s) may timeout
Claude Desktop (Windows/Mac)SupportedSame as Claude.ai

Note: Dispatch tools (agent calls like ask_policy_librarian) run multi-turn agent loops that take 5-15 seconds. The MCP server uses synchronous HTTP transport for maximum client compatibility. For operations that take minutes (report generation, deep policy research), use the web chat at eve.ev.energy.

Known Limitations​

  • No streaming for MCP tool calls — results are returned as a single JSON response after the tool completes. The web chat interface at eve.ev.energy provides real-time streaming for long operations.
  • No progress indicators — MCP clients see no feedback during tool execution. This is a limitation of the stateless HTTP transport required for broad client compatibility.