Encharge MCP Server

How to connect Encharge MCP to Claude Desktop

Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.

{
  "mcpServers": {
    "encharge": {
      "command": "npx",
      "args": ["-y", "<server-package-name>"],
      "env": {
        "ENCHARGE_API_KEY": "your-api-key-here"
      }
    }
  }
}
// Server source: https://github.com/khach-m/encharge-mcp
// Check the server's README for the exact "command" and required env vars.

Some MCP servers require an API key. Check the source page for setup: github.com/khach-m/encharge-mcp.

Does Encharge MCP cost extra?

The Encharge MCP server is community-built — free to run, but you still pay for your Encharge subscription.

• Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
• Your Encharge account still needs whatever plan is required to access the data the MCP server queries.
• Trade-off: zero MCP cost, but no guarantee it'll keep working when Encharge changes their UI or API.

Encharge also publishes a REST API

Encharge publishes an API, but per-tier gating wasn't extracted automatically.

What you can do with Encharge from an AI agent

Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.

Limits and gotchas

• Community MCP — not maintained by Encharge. Check the README and last-update date before depending on it.
• Fallback: the REST API works for any flow the MCP server doesn't cover.
• Rate limits: MCP calls count against your underlying Encharge API quota. Burst usage from a curious agent can drain a daily allowance fast.

Encharge MCP & API FAQ