Model Context Protocol
PLANNED

MCP Server

SDKs require developer integration. MCP exposes ExergyNet as callable tools for autonomous agents — no custom integration required.

IN DEVELOPMENT

The exergynet-mcp-server package is planned as part of Phase 8. The specification below reflects the intended interface. Subscribe to the GitHub repository for release announcements.

Why MCP

Agent-native access

The TypeScript SDK requires code-level integration. The MCP server exposes the same LNES-01 capabilities as structured, callable tools that autonomous agents can discover and invoke directly.

Any MCP-compatible agent runtime — Claude, ElizaOS, Swarms, custom orchestrators — can connect to ExergyNet without writing SDK integration code.

Package

Installation

GLOBAL INSTALL
npm install -g exergynet-mcp-server
Config

Agent configuration

Add ExergyNet to your agent's MCP server configuration:

claude_desktop_config.json / agent-config.json
{
  "mcpServers": {
    "exergynet": {
      "command": "npx",
      "args": ["exergynet-mcp-server"]
    }
  }
}
Tools

Exposed tools

exergynet_get_program_id READ
exergynet_get_metadata READ
exergynet_estimate_gate COMPUTE
exergynet_open_job WRITE
exergynet_settle_exergy SETTLE
exergynet_get_transaction_status READ
Alternative

SDK integration

If you need lower-level control, the TypeScript SDK is available now on npm.

Install SDK Agent manifest