AI Impact MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimate_impactA | Estimate the environmental impact (energy kWh, miles driven in a gas car, water for cooling, CO2e) for a single AI request given its token counts. Uses the EcoLogits life-cycle methodology. |
| log_usageB | Record one AI request's token usage into the local store so it shows up in reports. Use this to manually log usage from any client. |
| reportC | Summarize recorded AI usage and its environmental impact over a period (today, week, month, all), broken down by model. |
| efficiency_scoreA | Score how efficiently a conversation was set up (fewest prompts/rework). Pass the conversation turns. Returns a 0–100 score, grade, and actionable tips. |
| analyze_efficiencyA | Run the efficiency coach over your most recent Claude Code sessions (reads transcript text on-demand, never stores it). Returns per-session scores, an average, wasted-rework tokens, and your top recurring tips. |
| set_scenarioA | Set the default confidence scenario for future estimates. conservative = lowest (min active params), midpoint = mean, high = max. |
| scan_logsA | Backfill exact AI usage from Claude Code's local session transcripts (~/.claude/projects). Reads only token counts + metadata, never message content. Idempotent — safe to run repeatedly. |
| record_web_chatA | Record ESTIMATED usage for a Claude desktop/web conversation that doesn't expose token counts. Preferred: pass structured |
| generate_dashboardB | Build a standalone HTML dashboard (charts of energy/carbon/water over time and by model) from your recorded usage. Returns the file path to open in a browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/anchetadev/mata'
If you have feedback or need assistance with the MCP directory API, please join our Discord server