Design-partner early access
Add GreenCIO to Claude Code
Review GPU costs, inference economics, and power assumptions inside your development workflow.
Set up a local session
This setup requires Claude Code, Node.js 18 or later, and an approved local GreenCIO server build. Public package installation and live client compatibility are not yet verified.
Get the early-access setup
Request an approved server build and the API access your workflow needs. Keep the server on the computer that runs Claude Code.
Add the server configuration
Merge the entry below into
.mcp.jsonat your project root. Preserve existing server entries. Replace the example path with the server file path supplied during setup..mcp.json{ "mcpServers": { "greencio": { "command": "node", "args": [ "/absolute/path/to/greencio/mcp-server/dist/index.js", "--profile", "coding" ], "env": { "GREENCIO_BASE_URL": "https://www.greencio.com", "GREENCIO_DATA_API_KEY": "${GREENCIO_DATA_API_KEY:-}", "STRICT_NO_SYNTHETIC": "true" } } } }For keyed tools, set
GREENCIO_DATA_API_KEYin the environment that launches Claude Code. The configuration reads the key from that environment. Keep credentials out of project files.Check the connection
Start Claude Code in the project. Approve the project server when prompted. Run
/mcpand check that greencio is connected.Try the evidence question below. Confirm a GreenCIO tool call appears. A tool list alone does not verify upstream data access.
Try it
After setup, ask a question and check that the tool activity names GreenCIO. These are example prompts, not recorded results.
Use GreenCIO to find source-linked evidence about Meta datacenter projects from the last 30 days. Include publication dates and source links. State coverage gaps. Do not treat announcements as proof of operating capacity.
Use GreenCIO to estimate inference unit economics from assumptions I provide. Ask for missing inputs first. Show the inputs, calculation, and sensitivity to utilization. Separate submitted assumptions from observed prices.
Review this repository locally. Prepare only relative paths and these facts for GreenCIO: provider, region, gpu_type, gpu_count, replicas, utilization_rate, and model. Do not send source text, environment values, secrets, or absolute paths. Ask me for missing cost assumptions before estimating costs.
What to expect
- Calculations from your inputs
- Cost and payback estimates depend on the assumptions you submit. A power-readiness screen does not confirm utility service or a connection date.
- Sources and coverage limits
- Request observation dates and methodology for market data. Evidence search can return no matches or an unavailable response. Related news does not establish the cause of a price change.
- Access varies by tool
- Evidence search, payback estimates, and GPU-hour option analysis have no API-key requirement. They still use network services. Market data and other calculations require an authorized Data API key.
Troubleshooting
GreenCIO tools do not appear
Check that Node.js is available to the client and the configured server file exists. Restart the client. Check its MCP connection errors and your organization's tool policy.
A tool reports UPSTREAM_AUTH
Check that GREENCIO_DATA_API_KEY is available to the client process. Ask GreenCIO to confirm the key's access. Restart the client after changing its environment. Do not paste the key into chat.
Market data or evidence is unavailable
Check the requested market and period. Preserve the error or coverage gap in your answer. Do not replace missing observations with an unlabeled estimate.
Does this work in cloud sessions?
This guide covers local sessions. A cloud session cannot use a server path on your computer. GreenCIO cloud-client compatibility remains unverified.
How do I remove the connection?
Remove only the greencio server entry from your client configuration, then restart the client. Contact GreenCIO if you also need to revoke an issued API key.