About Boncourant
Boncourant is a hosted electricity-cost optimizer and auditor for people analyzing French power bills, contracts, and subscribed capacity. Its public tools cover retrospective bill analysis and prospective estimates, keeping those findings distinct.
Key features
- 01Analyze electricity bills and invoices
- 02Simulate electricity cost scenarios
- 03Check subscribed capacity
- 04Analyze renewal terms
- 05Assess PPA options
- 06Extract energy document data
Use cases
- 01Review charges on an electricity bill
- 02Compare capacity or contract scenarios
- 03Assess renewal terms and past choices
- 04Prepare energy documents for analysis
MCP support
The MCP server provides electricity-cost analysis tools to clients over a remote Streamable HTTP endpoint. No local installation is needed; available checks depend on the submitted evidence.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://boncourant.fr/mcpclaude mcp add --transport http fr-boncourant-boncourant https://boncourant.fr/mcp{"mcpServers":{"fr-boncourant-boncourant":{"type":"http","url":"https://boncourant.fr/mcp"}}}Open in Cursor{"servers":{"fr-boncourant-boncourant":{"type":"http","url":"https://boncourant.fr/mcp"}}}Open in VS Code{"mcpServers":{"fr-boncourant-boncourant":{"type":"http","url":"https://boncourant.fr/mcp"}}}{"mcpServers":{"fr-boncourant-boncourant":{"serverUrl":"https://boncourant.fr/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
19| Parameter | Type | Required | Description |
|---|---|---|---|
| audience | enum | No | household | professional | large_consumer | producer |
| capability_id | string | No | Exact identifier returned by a previous call. |
Details
From the project READMEBoncourant MCP
Public integration documentation for Boncourant, the French electricity-cost optimizer and auditor. This repository contains documentation and public discovery metadata for the hosted service.
Connect
- Endpoint:
https://boncourant.fr/mcp - Transport: Streamable HTTP
- Authentication: no account, API key or OAuth required for public tools
- Official registry name:
fr.boncourant/boncourant - Documentation: https://boncourant.fr/agents
- Live discovery manifest: https://boncourant.fr/.well-known/mcp.json
- OpenAPI: https://boncourant.fr/openapi.json
- Agent context: https://boncourant.fr/llms
Add the endpoint as a remote HTTP MCP server in your client. Clients using the mcpServers URL configuration format can use:
{
"mcpServers": {
"boncourant": {
"url": "https://boncourant.fr/mcp"
}
}
}
Client configuration formats vary; use your client's remote Streamable HTTP server instructions. No local package or server process is needed.
Capabilities
Start with list_capabilities to discover supported tasks, evidence requirements and limits. The public server exposes 19 tools as of 15 October 2026:
list_capabilities, hc_schedule_change_impact, simulate, analyze_bill, get_methodology, decompose_invoice, annualize_invoice, check_subscribed_power, analyze_renewal_terms, assess_historical_optimality, renewal_advisor, extract_energy_document, run_method, assess_ppa, create_analysis_study, get_analysis_study, get_analysis_report, eex_connector, pro_catalog.
Use the live manifest or MCP tools/list for current schemas. Available checks depend on the supplied evidence. Retrospective billing findings and prospective savings estimates are distinct; incomplete evidence does not establish a billing error or whole-market optimality.
Privacy and boundaries
The public MCP service does not expose private customer accounts, workspaces, Enedis consent, supplier switching or supplier outreach. Direct document extraction is non-retained. Asynchronous studies use opaque receipts; raw input is encrypted until processing ends, then erased, and results expire within 24 hours. Shared-service rate and size limits apply. Review the integration guidance and privacy policy before submitting documents.
Public metadata
server.json is the official registry publication descriptor. discovery.json is a dated snapshot of the public discovery manifest, not a replacement for live discovery. This repository does not contain the hosted application's implementation.
Contact: [email protected].
Version 1.5.1
Adds repository discovery metadata, clearer tool routing, and explicit temporary-study safety and receipt-access documentation. run_method is read-only. Creating an isolated study writes expiring state and may fetch an explicitly supplied document, so it remains non-destructive and idempotent, with readOnlyHint: false and openWorldHint: true. It never changes a customer account or supplier contract.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.