Manage Encharge people, tags, segments and fields, and track events for email automation. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"encharge": {
"url": "https://encharge.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"encharge": {
"type": "http",
"url": "https://encharge.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Encharge API key.
Optional: Write key (optional, for tracking events).
Find the API key and the write key in Encharge → Account → Account info. The API key needs a plan with API access. The write key is optional: only the event tracking tool uses it. Your keys are used only to call the Encharge API on your behalf; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Encharge API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
encharge_get_account | read | Get account The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info. |
encharge_get_people | read | Get people Look up people (contacts) by email, userId or Encharge id. Pass up to 20 people, each with at least one identifier. Returns each person with all fields, tags and segment data; a person that does not exist is left out. GET /people. |
encharge_list_segment_people | read | List people in a segment People in one dynamic segment, with paging (limit/offset), optional sort and a choice of person fields (attributes). Use encharge_list_segments for segment ids and encharge_list_fields for field names. GET /segments/{segmentId}/people. |
encharge_upsert_person | write | Create or update a person WRITE: create a person, or update the one that already has this email, userId or Encharge id. Only the fields you pass are set. Use encharge_add_tags for tags. POST /people. |
encharge_unsubscribe_person | write | Unsubscribe a person WRITE: unsubscribe one person so Encharge sends them no more email. The person stays in Encharge. Identify them by email, userId or Encharge id. POST /people/unsubscribe. |
encharge_add_tags | write | Add tags to a person WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags. |
encharge_remove_tags | write | Remove tags from a person WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags. |
encharge_list_segments | read | List segments List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments. |
encharge_list_fields | read | List person fields List all person fields (built-in and custom) with name, title, type and whether the field is read-only. Use the names in encharge_upsert_person. GET /fields. |
encharge_track_event | write | Track an event WRITE: record an event for a person through the Ingest API, for example "Registered user" or "Created Page". The person is created or updated from `user`. Use the event name "identify" to only create or update a person. Needs the account write key. POST https://ingest.encharge.io/v1/. |
encharge_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
encharge_request_feature | Request a missing feature Tell usefulapi that the user needs something the Encharge tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
encharge_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Encharge tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
encharge_cancel_subscription | Cancel the Pro subscription Cancel the caller's Encharge Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run encharge_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Encharge server only. Subscribe with encharge_upgrade (it returns a Stripe Checkout link). Cancel any time with encharge_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running encharge_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Encharge. The server calls the Encharge API with your own Encharge access, so it sees only the data that your account can see.
The login page asks for your Encharge API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Encharge API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Encharge API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Encharge.
Yes, if you approve it. 5 of the 10 Encharge tools can create or change data. The other 5 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Encharge server only. Run encharge_usage_status to see how many calls you used.
Ask the AI to run encharge_upgrade: it returns a Stripe Checkout link. To cancel, run encharge_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with encharge_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.