How to Use the Electricity Maps Carbon Intelligence MCP in Google ADK

Q: How do I configure the Electricity Maps Carbon Intelligence MCP Server with Google ADK?

You instantiate an McpToolset pointing to your Vinkius endpoint URL. Then you pass that toolset object into the tools list when building your LlmAgent.

Q: Can Google ADK restrict which Electricity Maps Carbon Intelligence tools run?

Yes. Use the toolnames argument during initialization. This prevents the agent from calling the zone listing tool if you only want it checking carbon intensity.

Feed live grid emissions data into your enterprise reasoning pipelines with Google ADK.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Electricity Maps Carbon Intelligence MCP to Google ADK

Create your Vinkius account to connect Electricity Maps Carbon Intelligence to Google ADK and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Electricity Maps Carbon Intelligence with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query global grids via Google ADK

The `get_carbon_intensity` tool connects your Gemini models directly to real-time regional emissions metrics. Agents submit a region code and instantly receive the current carbon cost of electricity in that exact location. Integrating this MCP Server into your Google Cloud environment bridges the gap between physical infrastructure and your data warehouse. Your agent pulls the live grid intensity, cross-references it with historical compute costs stored in BigQuery, and decides exactly where to route your next massive data processing job.

Inspect physical power sources

Calling the `get_power_production_breakdown` tool reveals the actual physics behind a local power grid. The response details the precise ratio of renewables, nuclear, and fossil fuels pushing electrons into the zone at that exact minute. Gemini's massive context window eats this data alive. You dump a week's worth of production breakdowns across fifty different regions straight into the prompt. The agent digests the entire million-token payload and outputs a highly specific, carbon-optimized deployment schedule for your global server fleet.

Discover available energy markets

The `list_energy_zones` tool provides the foundational map your AI client needs to navigate global energy markets. It outputs every valid geographical identifier that the system can actively monitor. Setting up this MCP Server takes one line of code using `McpToolset`. You wrap the endpoint URL in `StreamableHttpServerParameters` and pass it to the LlmAgent constructor. If you only want your agent checking specific metrics, the `tool_names` filter lets you restrict access to just the functions you actually need.

Setup guide

Set up Electricity Maps Carbon Intelligence MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Electricity Maps Carbon Intelligence tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Electricity Maps Carbon Intelligence_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Electricity Maps Carbon Intelligence tools via MCP.",
    tools=mcp_tools,
)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Electricity Maps. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Electricity Maps Carbon Intelligence now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Electricity Maps Carbon Intelligence MCP in Google ADK

You instantiate an `McpToolset` pointing to your Vinkius endpoint URL. Then you pass that toolset object into the `tools` list when building your LlmAgent.

Yes. Use the `tool_names` argument during initialization. This prevents the agent from calling the zone listing tool if you only want it checking carbon intensity.

The model reads the raw JSON responses natively. Because Gemini supports massive context windows, you loop these tool calls across dozens of zones without truncating the history.

No. Vinkius handles the underlying API credentials. Your application only needs its single endpoint token to authenticate with the sandbox.

The integration strictly handles location strings and ISO country codes. The isolated V8 environment processes these geography requests ephemerally, meaning zero traces of your cloud architecture or routing logic persist after the execution finishes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript