Skip to content
Agentmart
Submit a tool

Green MCP

Measure a program's CPU energy and LLM tokens, then refactor it cheaper.

Connector by rlawogh1005 · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Chalk Labs

Need help deploying Green MCP?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/rlawogh1005-green-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Measure a program's CPU energy and LLM tokens, then refactor it cheaper. Measure, never estimate.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
5 read · 0 write · 0 delete · 1 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 6

Read from the source code; the running server may list different tools.

Read 5 · Look things up without changing anything.

  • compare_energy
  • compare_tokens
  • energy_backend_info
  • measure_energy
  • measure_tokens

Not yet classified 1 · We could not tell from the name and description.

  • verify_equivalence

Tools (6)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • compare_energy

    Measure two commands and report which consumes less energy and by what margin. Only meaningful if both commands are functionally equivalent (same outputs for the same inputs) — verify that separately before drawing conclusions.

  • compare_tokens

    Measure two programs' token use and report which uses fewer, by how much. Only meaningful if both produce acceptable equivalent results — verify that separately (fewer tokens with worse answers is not a win).

  • energy_backend_info

    Report whether energy measurement is available on this host and which backend would be used. Call this before measure_energy to know if the energy axis works here — on a machine with no reachable CPU power sensor it returns energy_available: false, and you should rely on the token axis (or say energy can't be measured) rather than estimate.

  • measure_energy

    Measure the electrical energy (joules) a shell command consumes while running. Methodology: samples CPU package power at 100 ms during the run, subtracts a separately measured idle baseline, repeats the run (default 3x) and reports mean/stdev/CV. Use absolute paths; wrap any path containing spaces in double quotes. Expect ~(idle_seconds + repeats x runtime) of wall time.

  • measure_tokens

    Measure how many LLM tokens a program consumes when it runs (works on any machine — no special hardware). The program must read `base_url_env` for its LLM endpoint (most SDKs do); we point that at a non-blocking counting proxy forwarding to `upstream`, run the program, and report real provider `usage` (input/output/total tokens, call count). For a non-Anthropic target, pass its provider's base-url env var and upstream (e.g. OPENAI_BASE_URL, https://api.openai.com). If llm_calls is 0, the target didn't route through base_url_env.

  • verify_equivalence

    Run two commands and compare stdout + exit code. The gate before any energy/token comparison. With no stdin_inputs it's a single-input smoke test. Pass stdin_inputs (a list of strings fed to each program's stdin) to run an input BATTERY — all inputs must match. Stronger evidence still comes from running the project's own test suite.

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
33
Last commit
Aug 26, 2026 (2 months ago)
Last release
Jul 27, 2026 (3 months ago)
Last package publish
Jul 27, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.rlawogh1005/green-mcp
Version
0.1.2
Auth
No auth
Packages
pypi green-mcp
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get Green MCP running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying Green MCP?

CallGet help
Cite this page

Green MCP. Agent Mart. https://agentmart.dev/connectors/rlawogh1005-green-mcp (last updated 2026-10-24)