<ul> <li>🦫 <b>Go</b> (latest version recommended)</li> <li>🔑 <b>Conso API token</b> — register for free at conso.boris.sh</li> <li>🆔 <b>PRM
Most monitoring and observability work still happens through a UI a human drives. Enedis Linky MCP server moves it into the conversation instead. 🦫 Go (latest version recommended) 🔑 Conso API token — register for free at conso.boris.sh 🆔 PRM number — your 14-digit Linky meter identifier (found on your electricity bill) .
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 5 tools. What each one is for:
get_daily_consumption — Daily electricity consumption (Wh) for a date rangeget_load_curve — 30-minute average power readings (W)get_max_power — Maximum power reached each day (VA)get_daily_production — Daily solar production (Wh) for solar installationsget_production_load_curve — 30-minute average production power readings (W)Configuration is passed through the environment: CONSO_API_TOKEN, LINKY_PRM, MCP_TRANSPORT, PORT, LINKY_DASHBOARD, CONSO_API_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Enedis Linky's toolset — get_daily_consumption, get_load_curve, get_max_power and 2 more — is a fair guide to whether it matches your workflow. It is maintained by mjrgr; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Enedis Linky's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_daily_consumption | Daily electricity consumption (Wh) for a date range |
| get_load_curve | 30-minute average power readings (W) |
| get_max_power | Maximum power reached each day (VA) |
| get_daily_production | Daily solar production (Wh) for solar installations |
| get_production_load_curve | 30-minute average production power readings (W) |
{
"mcpServers": {
"linky": {
"command": "/absolute/path/to/bin/enedis-linky-mcp-server",
"env": {
"CONSO_API_TOKEN": "your_token_here",
"LINKY_PRM": "12345678901234"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CONSO_API_TOKEN | Credential the server authenticates with. | Yes |
| LINKY_PRM | Configuration value read at startup. | Optional |
| MCP_TRANSPORT | Configuration value read at startup. | Optional |
| PORT | Configuration value read at startup. | Optional |
| LINKY_DASHBOARD | Configuration value read at startup. | Optional |
| CONSO_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.