Model Context Protocol (MCP) Servers

Ecosystem Overview

The Model Context Protocol (MCP) is an open standard that enables AI models and agentic harnesses to securely discover and invoke external tools and read structured resources.

The Asoba open-source ecosystem provides both specialized MCP servers that expose energy and macroeconomic data to any AI client, and Nehanda CLI, an agentic REPL and execution harness that acts as a first-class MCP client.

graph TD
    subgraph Clients["MCP Clients"]
        NC["Nehanda CLI<br/>(Asoba Agentic REPL)"]
        CD["Claude Desktop"]
        CU["Cursor / VS Code"]
    end

    subgraph Middleware["Client-Side Middleware"]
        EM["ODSE Energy Middleware<br/>(Automatic Inverter Normalization)"]
    end

    subgraph Servers["Asoba MCP Servers (stdio JSON-RPC)"]
        SDK["asoba-mcp-server<br/>(Asoba / Ona Platform SDK)"]
        ZOR["zorora-mcp-server<br/>(Zorora Economic Data)"]
    end

    subgraph Backends["Data Sources & APIs"]
        ONA["Ona Energy Platform<br/>(Inverters, OODA, JEPA, Forecasts)"]
        ZAPI["Zorora AWS Fargate API<br/>(FRED, Yahoo Finance, World Bank, Ember, SAPP, Eskom)"]
    end

    NC --> EM
    EM --> SDK
    EM --> ZOR
    CD --> SDK
    CD --> ZOR
    CU --> SDK
    CU --> ZOR

    SDK --> ONA
    ZOR --> ZAPI

Available MCP Servers

Asoba Platform SDK MCP Server

The Asoba Platform SDK MCP Server (asoba-mcp-server) wraps the Python SDK for the Ona Energy Management Platform. It allows any MCP-compatible AI assistant to inspect solar asset telemetry, monitor live OODA/JEPA state detections, query pre-computed site KPI rollups, retrieve predictive maintenance task lists, and fetch device or site-level solar energy forecasts.

Installation & Launch

Install the SDK with the [mcp] extra:

pip install "asoba[mcp]"

Run directly over stdio:

# Direct module execution
python -m asoba.mcp_server

# Or using the console entrypoint
asoba-mcp-server

# Or using uvx (zero-install execution for MCP clients)
uvx --from "asoba[mcp]" asoba-mcp-server

Environment Variables

Tools

1. Inverter Telemetry Tools

2. OODA Terminal Alert Tools

3. Partner API Snapshots

4. Solar Forecasting Tools

Resources (JSON Schemas)

The server exposes JSON schemas via the schema:// URI scheme so models can inspect the shape of responses on demand:

Zorora Economic Data MCP Server

The Zorora Economic Data MCP Server (zorora-mcp-server) provides access to 80 macroeconomic and energy market time series through the Zorora platform.

All heavy lifting — upstream fetching from 6 data providers, SQLite caching on AWS EFS, and data transformation — runs server-side on Zorora’s AWS Fargate cluster. The MCP server is a lightweight client requiring only requests and mcp.

Upstream Data Coverage

Tools

Environment Variables

Nehanda CLI Integration

Nehanda CLI is built to consume MCP servers natively. Rather than requiring external sidecars or gateway daemons, Nehanda CLI’s engine manages MCP server child processes directly over stdio.

How Nehanda CLI Uses MCP

1. Automatic Discovery & Namespacing: At startup and turn execution, Nehanda CLI connects to each configured server in mcp.json, retrieves tool definitions via tools/list, and injects them into the model’s active tool list under the mcp__<server>__<tool> namespace.
2. Built-in Resource Tools: Nehanda CLI includes ListMcpResources and ReadMcpResource tools, allowing the model to inspect schema resources (such as schema://KPIRollup) dynamically.
3. ODSE Energy Middleware: Telemetry and alert responses from energy MCP servers pass through Nehanda CLI’s built-in ODSE normalization layer, automatically mapping OEM payload structures into standard energy schema types.
4. Interactive REPL Control: Configure and manage servers directly in the terminal:

   ❯ /mcp status                         # View registered MCP servers
   ❯ /mcp list                           # Discover all tools across active servers
   ❯ /mcp reload asoba                   # Invalidate cache and reload a specific server
   ❯ /mcp env asoba ASOBA_API_KEY sk-*** # Set an API key interactively
   

Client Configuration Examples

1. mcp.json (Nehanda CLI & Project Repositories)

Place in ./mcp.json (project root) or ~/.config/nehanda/mcp.json (user global):

{
  "mcpServers": {
    "asoba": {
      "command": "python3",
      "args": ["-m", "asoba.mcp_server"],
      "env": {
        "ASOBA_API_KEY": "your-asoba-api-key"
      }
    },
    "zorora-economic-data": {
      "command": "python3",
      "args": ["-m", "mcp_server.server"],
      "cwd": "/path/to/zorora",
      "env": {
        "ZORORA_API_URL": "https://p0c7u3j9wi.execute-api.af-south-1.amazonaws.com/prod/api/v1"
      }
    }
  }
}

2. Claude Desktop (claude_desktop_config.json)

Configure in ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "asoba": {
      "command": "uvx",
      "args": ["--from", "asoba[mcp]", "asoba-mcp-server"],
      "env": {
        "ASOBA_API_KEY": "your-asoba-api-key"
      }
    },
    "zorora-economic-data": {
      "command": "python3",
      "args": ["-m", "mcp_server.server"],
      "cwd": "/path/to/zorora",
      "env": {
        "ZORORA_API_URL": "https://p0c7u3j9wi.execute-api.af-south-1.amazonaws.com/prod/api/v1"
      }
    }
  }
}

3. Cursor / VS Code MCP Configuration

Configure inside .cursor/mcp.json or your VS Code MCP extension settings:

{
  "mcpServers": {
    "asoba": {
      "command": "uvx",
      "args": ["--from", "asoba[mcp]", "asoba-mcp-server"],
      "env": {
        "ASOBA_API_KEY": "your-asoba-api-key"
      }
    },
    "zorora-economic-data": {
      "command": "python3",
      "args": ["-m", "mcp_server.server"],
      "cwd": "/path/to/zorora"
    }
  }
}