広告掲載
MCP.so
ログイン

Tidegap MCP Server

@Vitalini

リポジトリホームページ

基本情報

カテゴリ

AI とエージェント

トランスポート

stdio

作者

Vitalini

投稿者

Vitalii Borovyk

Tidegap MCP Server について

Open-source MCP server that defers non-urgent LLM tasks to the cleanest grid hour before a deadline.

#carbon-aware#scheduler#batch-api#claude-code#openclaw#sustainability#green-software#mcp#anthropic#openai#grid-intensity

Tidegap MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

Tidegap MCP Server のツール

9

Return the projected electricity-grid carbon intensity for a region, hour by hour. Use this when deciding whether to run an expensive AI task now or defer it — intensity is reported in grams CO2-equivalent per kWh with a categorical band (very_clean / clean / average / dirty / very_dirty). Read-only; does not touch the task queue.

Return the optimal carbon-aware execution window for a task WITHOUT scheduling it. Use this for non-committal planning — to see when the cleanest grid moment falls inside the deadline (and the savings vs running now) before deciding whether to commit via schedule_task. Returns the chosen window, top alternatives, a batch_eligible flag, the grid_source (which feed produced the forecast — 'mock' means synthetic data), and a one-line reasoning string. Read-only; does not touch the task queue.

Queue an AI task to run during off-peak hours inside the given deadline. Four parallel wins: (1) lighter on the electricity grid — deferring non-urgent tasks smooths projected AI compute demand; (2) up to 50% cheaper — auto-routes through Anthropic/OpenAI Batch APIs when the deadline allows; (3) faster sync calls — off-peak queues are shorter; (4) lower carbon — dispatch at the cleanest electricity-grid hour. Invoke this tool whenever the user phrases a request with deferral language: "do this later", "by tomorrow", "tonight", "overnight", "by EOD", "sometime this week", "when you have a moment", "remind me to", "queue this up", "schedule this", "no rush", "not urgent". Convert the user's wording to an ISO-8601 deadline and pass the task as the prompt. Returns a task_id you can later check with check_queue_status. Good fits: nightly digests, batch summaries, research sweeps, evaluator runs, multi-step report generation — anything the user is fine waiting on. Do NOT use for live chat, interactive code edits, or any task the user is actively waiting to see complete.

Report on the ebb-ai task queue. With no arguments, returns a summary of all known tasks (including tasks persisted by previous sessions — the queue survives host restarts). With task_id, returns full detail for one task including any carbon receipt (estimated vs actual grams, grid_source, energy_source). Read-only.

Cancel a queued or scheduled task. Idempotent — if the task is already completed/failed/cancelled this returns the existing status without error. Throws only if task_id is unknown.

Dispatch a queued or scheduled provider-call task immediately, bypassing the scheduler's chosen carbon window. The resulting receipt records intensitySource='expedited'. Only provider-call tasks still queued/scheduled can be expedited; running, submitted (awaiting Batch API results), or terminal (completed/failed/cancelled) tasks are rejected with an explanatory error.

Re-score and reschedule a queued or scheduled task against a new deadline; the scheduler re-picks the cleanest window inside it. Throws if the task is already running or terminal, or if the new deadline is invalid or in the past.

Re-dispatch a failed provider-call task. Only valid when the task's current status is 'failed' — queued/scheduled/running/submitted/completed tasks are rejected with an explanatory error. The new run's receipt overwrites the old.

Bulk-cancel every task in the queue that is still cancellable (status queued or scheduled). Running/completed/failed/cancelled tasks are left untouched. Optionally filter by status. Returns the number of tasks cancelled.

概要

What is tidegap?

A workload scheduler for the agentic-AI economy that defers non-urgent LLM tasks to cheap, low-load grid windows. It integrates with MCP (Model Context Protocol) to offer automatic carbon‑ and cost‑aware scheduling and ships as an npm package and a one‑command Claude Code plugin.

How to use tidegap?

Install via npm install -g @tidegap/mcp or as a Claude Code plugin (claude plugin install tidegap). Add to Claude Desktop’s MCP config. Use MCP tools (get_grid_forecast, schedule_task, check_queue_status) or the @tidegap/core library. A Python 3.11+ port is also available.

Key features of tidegap

  • Automatic deferral of tasks to off-peak grid windows.
  • Real-time carbon‑intensity forecasts for 31 grid regions.
  • 50% cost savings through Anthropic and OpenAI Batch APIs.
  • Auditable carbon and cost receipts for every dispatch.
  • SQLite‑backed durable queue with retry‑with‑backoff.
  • Nine MCP tools for agent hosts (Claude Desktop, Cursor, etc.).
  • One‑command Claude Code plugin with slash commands.

Use cases of tidegap

  • Defer overnight summaries, batch analysis, and compliance scans to cleaner grid windows.
  • Reduce inference costs by routing deadline‑tolerant work through Batch APIs.
  • Smooth data‑center load curves and support ESG reporting with carbon receipts.
  • Schedule document processing with deadline‑aware, grid‑optimal timing.

よくある質問

1

What dependencies or runtime are required?

Node.js for the npm packages (`@tidegap/core`, `@tidegap/mcp`); Python 3.11+ for the Python port. Anthropic and OpenAI SDKs are optional peer dependencies.

2

Where does data live?

Grid forecasts are fetched from public APIs (UK National Grid ESO, US EIA, ENTSO‑E, Electricity Maps). The task queue persists locally to `~/.tidegap/queue.db`.

3

What transports and auth does it use?

The MCP server communicates over stdio. No authentication is required for the MCP server itself; optional API keys are needed for some grid data sources. Provider SDKs handle Batch API auth.

4

What are known limits?

Version v0.18.0, 88+ tests pass. Some grid regions require API keys and fall back to mock data without one. WattTime marginal‑emissions support is on the roadmap.

5

How does it compare to alternatives?

The README does not discuss alternatives. tidegap is focused on carbon‑aware scheduling with native MCP integration for agentic AI workloads.

コメント

「AI とエージェント」の他のコンテンツ

CrawlForge MCP Server

mysleekdesigns

28-tool MCP server for web scraping, crawling, deep research & autonomous extraction — clean Markdown & structured JSON for Claude, Cursor & any MCP client. 1,000 free one-time credits, local-Ollama LLM support.

2

treg.to

Jason Zhou

OpenRouter for tools & data — 3,028 APIs for your agent, one token, pay per call. treg.to is a remote MCP server at https://treg.to/mcp/ that gives an agent 3,028 ready-to-call API endpoints across 82 platforms: SEO and

Gemina

Gemina Tech Ltd.

Extract, search and tag any document — invoices, receipts, contracts, forms, or your own templates. 13 tools, one sign-in (OAuth 2.1) or API key, free FileTag tier, data residency in the EU, US, Israel or Asia.

Agentic Atlas

Avery Jones

Consult field-tested agent-system design patterns through 8 hosted, read-only tools for orientation, deep reading, relationships, provenance, glossary terms, and publication decisions.

KissCode

NickSF189

KissCode is the world's first relationship network where AI agents and people meet. Connect your agent over MCP: it gets a profile, meets other agents and real people, chats, sends virtual gifts, goes on dinner and movie

広告掲載