Regenerative Compute

Add Regenerative AI to your AI coding assistant in 30 seconds.

Every AI session consumes energy. This MCP server lets your AI assistant estimate that footprint and retire verified ecocredits on Regen Network — with immutable on-chain proof.

This is regenerative contribution, not carbon offsetting. No neutrality claims. Just verified funding of ecological regeneration.

Install

claude mcp add -s user regen-compute -- npx regen-compute

That's it. Works immediately — no API keys, no wallet, no configuration needed for read-only tools.

Supported Platforms

{
  "mcpServers": {
    "regen-compute": {
      "command": "npx",
      "args": ["regen-compute"]
    }
  }
}

{
  "mcpServers": {
    "regen-compute": {
      "command": "npx",
      "args": ["regen-compute"]
    }
  }
}

{
  "servers": {
    "regen-compute": {
      "command": "npx",
      "args": ["regen-compute"]
    }
  }
}

{
  "mcpServers": {
    "regen-compute": {
      "command": "npx",
      "args": ["regen-compute"]
    }
  }
}

{
  "mcpServers": {
    "regen-compute": {
      "command": "npx",
      "args": ["regen-compute"]
    }
  }
}

name: Regenerative Compute
version: 0.0.1
schema: v1
mcpServers:
  - name: regen-compute
    type: stdio
    command: npx
    args:
      - "regen-compute"

npm install -g regen-compute

{
  "openctx.providers": {
    "https://openctx.org/npm/@openctx/provider-modelcontextprotocol": {
      "nodeCommand": "node",
      "mcp.provider.uri": "file:///ABSOLUTE/PATH/TO/node_modules/regen-compute/dist/index.js"
    }
  }
}

{
  "mcpServers": {
    "regen-compute": {
      "command": "npx",
      "args": ["regen-compute"]
    }
  }
}

ChatGPT and OpenAI API: These platforms require a remote HTTP MCP server (streamable HTTP or SSE transport). Regenerative Compute currently uses stdio transport. HTTP transport support is on the roadmap.

What You Get

Three payment modes — pick what works for you

1. Credit card (default, no setup) — get a Regen Marketplace link
2. Direct on-chain — set REGEN_WALLET_MNEMONIC, retire in a single tx
3. Any token, any chain — USDC on Base, ETH on Arbitrum, etc. via ecoBridge

How It Works

Your AI Assistant (Claude Code / Cursor / etc.)
    │
    │ MCP Protocol (stdio)
    ▼
Regenerative Compute MCP Server
    │
    ├─ Footprint estimation (heuristic, clearly labeled as approximate)
    ├─ Credit browsing (live sell order data from Regen Ledger)
    ├─ Retirement execution (MsgBuyDirect with auto-retire)
    └─ Certificate retrieval (on-chain verification)
    │
    ▼
Regen Network Ledger (immutable, verifiable, non-reversible)

If anything fails during on-chain retirement, it falls back to a marketplace link. Users are never stuck.

Configuration

Works with zero config. Set environment variables for advanced features:

cp .env.example .env

See .env.example for all options with inline documentation.

MCP Prompts

Pre-built workflows you can invoke:

Credit Types

Data Sources

Development

Local setup

git clone https://github.com/regen-network/regen-compute.git
cd regen-compute
npm install
cp .env.example .env  # fill in your keys (optional — read-only tools work without)
npm run build

Connect to Claude Code (local build)

Point your MCP config at the local build so changes are reflected immediately:

claude mcp add regen-compute -s user -- node /path/to/regen-compute/dist/index.js

To enable ecoBridge tools locally:

claude mcp add regen-compute -s user \
  --env ECOBRIDGE_ENABLED=true \
  -- node /path/to/regen-compute/dist/index.js

Scripts

Running tests

npm test              # single run
npm run test:watch    # re-run on file changes

Tests mock all external APIs (RPC providers, ecoBridge, Regen Ledger) — no network calls, no wallets needed.

Roadmap

See ROADMAP.md for the full 3-track rollout plan, dependency graph, and business context.

Contributing

We welcome contributions! See CONTRIBUTING.md for the issue workflow, label guide, and branch conventions.

Good first issues: gh issue list --label "good first issue"

License

Apache-2.0 — see LICENSE.