ebb-ai

io.github.VitaliniPublished by GitHub account Vitaliniv0.17.0Updated Nov 6, 2026

Runs non-urgent LLM tasks at the cleanest grid hour before a deadline, via Batch APIs when allowed.

VerifiedSTDIODesktop onlyProductivity & WorkflowCloud & InfrastructureAI & ML

Overview

AI-generated overview

Queues non-urgent LLM tasks to run at the lowest-carbon grid hour before a deadline, using provider Batch APIs when time allows.

What you can do
  • Plan and queue tasks: recommend the cleanest window inside a deadline, schedule one-off or recurring tasks, set a carbon budget or earliest start.
  • Inspect and manage the queue: check status and carbon receipts, cancel one task or a whole series, cancel all pending work.
  • Adjust timing: postpone to a preset or delay, update the deadline, expedite now, retry failed tasks.
  • Read grid data: hour-by-hour carbon intensity forecast for a region.
  • Continue and report: reply to a completed task, and read local subscription limits and an optional spend estimate.
When to use it
Useful when an agent is asked to do something "tonight" or "by tomorrow" and the work is not urgent, so it can be deferred to a cleaner grid hour. Also handy for recurring background jobs where timing is flexible and carbon matters.
Requirements
Runs locally over stdio, typically via npx, so Node.js is needed. A region defaults to GB; other zones need free keys or accounts: EIA, ENTSO-E, WattTime username and password, or Electricity Maps. Running tasks through Anthropic or OpenAI needs the matching API key; without a grid key the server falls back to mock data. A tick daemon must be installed for queued tasks to run.
Before you install
Several secrets are requested: ANTHROPIC_API_KEY, OPENAI_API_KEY, EBB_EIA_API_KEY, EBB_ENTSOE_SECURITY_TOKEN, EBB_ELECTRICITY_MAPS_API_KEY and WATTTIME_PASSWORD, plus a WattTime username. Scheduled tasks spend money on provider APIs, and the usage tool can estimate list-price cost. Tasks write results to files and a local SQLite queue, and can wake an idle Claude Code session. The README documents a rename to a different package and variable prefix than the manifest lists, so confirm which…

Installation

In SourceWeft

  1. Open ebb-ai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Tidegap]

@tidegap/mcp

Renamed from @ebb-ai/mcp in 0.18.0. Use the host config key tidegap and npx -y @tidegap/mcp; the ebb-mcp bin and the EBB_* variables were removed in 0.19. See Renamed from Ebb AI.

MCP server that lets your agent run non-urgent LLM tasks at the cleanest grid hour before a deadline.

Add it to any MCP host. When a user says "do this tonight" or "by tomorrow", the agent calls schedule_task. Tidegap then runs the task at the lowest-carbon grid hour before the deadline, and through the provider Batch API when the deadline allows.

  • 12 MCP tools (measured), among them recommend_window, schedule_task, check_queue_status, get_grid_forecast, cancel_task, postpone_task, update_deadline.
  • Live 72-hour forecast. GB needs no key; other regions use free keys (EIA, ENTSO-E, WattTime, Electricity Maps).
  • One signed carbon receipt per task, stored in ~/.tidegap/queue.db.
bash
npx -y @tidegap/mcp
json
{ "mcpServers": {    "tidegap": { "command": "npx", "args": ["-y", "@tidegap/mcp"] }} }

Proof: one real GB run, 2026-09-30. Forecast peak 183 gCO2/kWh vs recommended window 88 gCO2/kWh, about 52 % lower for this run only (forecast, projected). Receipt at dispatch: 158 gCO2/kWh (measured). Host-specific configs: https://www.tidegap.com/docs#install

Run

bash
npx -y @tidegap/mcp

The server speaks MCP over stdio. To wire it into an agent client:

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (Linux/Windows have similar paths):

json
{  "mcpServers": {    "tidegap": {      "command": "npx",      "args": ["-y", "@tidegap/mcp"],      "env": {        "TIDEGAP_ELECTRICITY_MAPS_API_KEY": "optional - mock data without it",        "TIDEGAP_DEFAULT_REGION": "US-CAL-CISO"      }    }  }}

Restart Claude Desktop after editing.

Claude Code

Add tidegap to your ~/.claude/mcp.json (or workspace .claude/mcp.json):

json
{  "mcpServers": {    "tidegap": {      "command": "npx",      "args": ["-y", "@tidegap/mcp"]    }  }}

OpenClaw

Add to ~/.openclaw/mcp.json:

json
{  "mcpServers": {    "tidegap": {      "command": "npx",      "args": ["-y", "@tidegap/mcp"]    }  }}

Tools exposed (12, measured)

ToolPurpose
schedule_task(... repeat?, every_hours?, days?, window?, time_zone?) with repeat daily, weekdays, weekly or every_n_hoursCreate a recurring job: each run is a new task at the cleanest hour of its period. End it with cancel_task(series: true).
get_grid_forecast(region, hours?)Hour-by-hour carbon intensity for a region; useful before deciding whether to defer.
recommend_window(deadline, region?, ...)Plan the cleanest window inside the deadline without queueing anything.
schedule_task(prompt, deadline, model?, region?, carbon_budget_g?, repeat?, origin_session_id?, not_before?)Queue a task to run in the cleanest window inside the deadline. Returns a task_id and one line that says whether it will run: Runs at <time> local., or the readiness sentence with its fix, for example Tasks will not run: no tick daemon. Run `tidegap install`.. not_before sets the earliest start. repeat defaults to none, also for deadline_kind: "quota_reset".
schedule_task(... runner?, cwd?, permission_profile?, result_path?, wake_session?)Hand off the work shape: runner is another name for provider; cwd is the folder a claude-code run works in (another folder than the session's runs fresh there); permission_profile is read, web or none (read with a cwd); result_path is a new file Tidegap writes the result text to, inside cwd, the session's project folder or the temp folder. wake_session: true wakes the idle Claude Code session that queued the task when it finishes (within 12 hours after its last turn; refused outside a session). runner or provider command is refused with the tidegap queue add --runner command line. output_path follows the same folder rules.
check_queue_status(task_id?)Inspect the queue or one specific task; includes a carbon receipt once the task has completed.
cancel_task(task_id, series?)Cancel a queued or scheduled task; on a repeating task, skip it, or end the series with series: true.
reply_task(task_id, text, deadline?)Continue a completed task: a new task with the conversation plus this text, same provider and model.
expedite_task(task_id)Dispatch a queued or scheduled task now, outside its carbon window.
postpone_task(task_id, preset? | until? | delay_minutes?, reset_at?)"Later": move a pending task later, never earlier. Presets 1h, tonight (22:00 to 06:00), tomorrow_morning (09:00 to 12:00), after_limit_reset (5 minutes after the Claude limit reset: reset_at, else this machine's limit reading, else a reset time given before).
update_deadline(task_id, deadline)Reschedule a task against a new deadline.
retry_task(task_id)Re-dispatch a failed task.
cancel_all(status?)Cancel every task that is still queued or scheduled.
tidegap_usage(include_spend?)Read-only: the Claude Code subscription limits of this machine and when they reset, and the Codex limits from its local logs. include_spend adds the current 5-hour window's tokens and an API list-price cost estimate.

Environment variables

These variables configure this MCP server (and the tidegap CLI, which reads the same set). They are read at the server's own entry point and injected into @tidegap/core, which is environment-pure and reads nothing ambient itself.

OpenClaw plugin users: the @vitalini/tidegap OpenClaw plugin reads no environment variables. Configure it through plugin config instead, under plugins.entries.tidegap.config in your gateway config — the "Plugin config" column below names the field that replaces each variable. OpenClaw resolves the "${ENV_VAR}" shorthand in those fields, so you can keep exporting the same variables and let the gateway read them on the plugin's behalf.

VarPlugin configPurpose
TIDEGAP_ELECTRICITY_MAPS_API_KEYelectricityMapsApiKeyAPI key from electricitymaps.com. Universal fallback. If unset (and no zone-specific feed is configured), the server falls back to deterministic mock data so you can still run the whole stack locally.
TIDEGAP_EIA_API_KEYeiaApiKeyFree US EIA key. Enables average-emissions intensity for the US ISO zones (CAISO / ERCOT / ISO-NE / NYISO / PJM / MISO).
TIDEGAP_ENTSOE_SECURITY_TOKENentsoeSecurityTokenFree ENTSO-E token. Enables EU zone intensity (FR / DE / ES / IT / NL).
WATTTIME_USERNAME + WATTTIME_PASSWORDwattTimeUsername + wattTimePasswordFree WattTime v3 account. Enables marginal-emissions (co2_moer) forecasts for the US ISO zones — takes precedence over EIA where covered, falls through to EIA on any error. The marginal signal is disclosed as signalType: "marginal" on forecasts and receipts.
TIDEGAP_DEFAULT_REGIONdefaultRegionRegion when a tool call names none. Beats the stored region setting; see Grid region.
ANTHROPIC_API_KEYanthropicApiKeyEnables the anthropic provider (batch-capable).
OPENAI_API_KEYopenaiApiKeyEnables the openai provider (batch-capable).
GEMINI_API_KEY / GOOGLE_API_KEYgeminiApiKey / googleApiKeyEnables the gemini provider (Generative Language API, sync-only). GEMINI_API_KEY is preferred; GOOGLE_API_KEY is the fallback.
OLLAMA_HOSTollamaHostEnables the local ollama provider (sync-only). Default http://localhost:11434; keyless — set this var to opt the provider in.

Grid region

The server resolves the region of each tool call in this order:

  1. the tool call's region argument,
  2. TIDEGAP_DEFAULT_REGION in the server's environment (the agent host's MCP config),
  3. the region setting stored on this machine: tidegap region set <zone>, or Settings → Grid region in tidegap ui and the Mac app (key TIDEGAP_DEFAULT_REGION in ~/.tidegap/config),
  4. a guess from the machine's time zone,
  5. GB.

The server reads the setting again when the file changes, so a new setting applies on the next tool call with no restart. A stored value that is not a supported zone is ignored, with one stderr warning per change. schedule_task replies carry region_source: flag | env | setting | timezone | fallback.

A region argument must be one of the 31 supported zones (any case). Another value is rejected with the closest zones and a link to request a region, for example Unknown zone UA. Closest: PL. Request a region: <link>. With TIDEGAP_ELECTRICITY_MAPS_API_KEY set, any zone passes, because Electricity Maps serves zones beyond the list; with TIDEGAP_ENTSOE_SECURITY_TOKEN set, IT passes too.

Develop

From the root of a clone of https://github.com/tidegap/tidegap:

bash
pnpm installpnpm --filter @tidegap/mcp buildnode packages/mcp-server/dist/server.js

Source: packages/mcp-server/README.md at commit 11e1df5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.17.0LatestOct 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts