GreenAI Network MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GreenAI Network MCP ServerHow much energy did the GreenAI Network use today?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GreenAI Network MCP Server for Alexa+
Ask Alexa+ about a real AI compute network — and get measured answers.
GreenAI Network is a distributed, sustainable AI compute network coordinated by a swarm of AI agents. This project exposes the network's live telemetry to Alexa+ (and any MCP client) through a self-hosted Model Context Protocol server using the Streamable HTTP transport (MCP spec 2025-11-25).
Every answer comes from the network's public telemetry endpoint
(https://www.greenainetwork.com/api/sala) and reflects the network right
now: nodes online, active agents, responses served, and — the point of
GreenAI — energy measured on the hardware (real GPU watts per response,
idle draw subtracted). What cannot be measured is never estimated or shown.
Tools
Tool | What it answers |
| Nodes online, active agents in the swarm, responses served today and success rate. |
| Measured Wh, Wh per response, metered responses, solar node state, measurement policy. |
| Per-node GPU utilization, VRAM and live power draw. |
Example questions an Alexa+ user can ask:
“How is the GreenAI Network doing right now?”
“How much energy did the network use today?”
“What is the solar node drawing at the moment?”
Related MCP server: Lifesign
Run it
pip install -r requirements.txt
python server.py
# MCP endpoint: http://localhost:8000/mcp (Streamable HTTP)Verify with the bundled test client (starts from a second terminal while the server is running):
python test_client.pyIt performs the MCP initialize handshake (negotiating protocol
2025-11-25), lists the tools and calls each one against the live network.
Security / privacy
The server is read-only and consumes a public telemetry endpoint.
It holds no credentials, tokens or secrets of any kind — there is nothing to configure and nothing sensitive in this repository.
It exposes no internal addresses: the only outbound call is the public
https://www.greenainetwork.com/api/sala.
What was built for this hackathon
The GreenAI Network itself (nodes, agent swarm, telemetry) predates the hackathon and is live in production. Built during the hackathon window: this MCP server, its tool layer over the public telemetry API, and the Alexa+ integration described above.
License
MIT — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Streamable HTTP MCP server exposing planner flows, tasks, and squads.
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to read real-time device status and health data (battery, location, network) reported from a mobile phone, acting as a single-port HTTP/MCP telemetry server.1-
- AlicenseNot gradedqualityBmaintenanceExposes server-management and operational data to MCP-aware clients and AI agents, providing tools to search servers, fetch metrics and system stats, and create or retrieve alerts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to call a hello tool and access observability features, including metrics and request traces, through a Streamable HTTP transport with SQLite-backed storage.221 npmMIT