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.
Skip the dashboard, ask Claude
- "What campaigns underperformed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Encharge data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Encharge account
- Multi-account workflows without context-switching the Encharge UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Encharge data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Encharge safe
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.
- Auth flow: MCP servers usually inherit the underlying API auth method (unknown). Expect to configure that on first install.
- Rate limits: MCP calls count against your underlying Encharge API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Moderate agent-fit with community support. Encharge has a community MCP server and documented API with Node SDK, plus native ChatGPT integration, but lacks official MCP hosting, OpenAPI specs, and Claude native support. The missing structured outputs and webhooks limit real-time automation workflows.
Scored 2026-05-21 by Joonas (TMB).
Encharge MCP & API FAQ
Is the Encharge MCP server official?+
Can I use the Encharge MCP with Cursor or Codex?+
Does Encharge have a public API?+
Which LLMs does Encharge integrate with directly?+
Sources
- Encharge official site: https://encharge.io
- MCP server page: https://github.com/khach-m/encharge-mcp
- API docs: https://encharge.io/integrations/api/
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

