Encharge MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi

Manage Encharge people, tags, segments and fields, and track events for email automation.

Deletes · 4Changes · 1

Compare Registry entry

10 tools: 4 can delete or cancel things, 1 change things and 5 only read.

Scanned Oct 21, 2026

Deletes or cancels4Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things1Claude Code: ask: see these tools
Only reads5Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http encharge https://encharge.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

10 tools

Deletes or cancels 4Removes, cancels or revokes something.Claude Code: deny

encharge_remove_tagsWRITE: remove one or more tags from an existing person.No findings
Why it is in this group
- The name "encharge_remove_tags" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags.
Annotations the server declares
- title: Remove tags from a person
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
encharge_track_eventWRITE: record an event for a person through the Ingest API, for example "Registered user" or "Created Page".No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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/.
Annotations the server declares
- title: Track an event
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
encharge_unsubscribe_personWRITE: unsubscribe one person so Encharge sends them no more email.No findings
Why it is in this group
- The name "encharge_unsubscribe_person" says "unsubscribe": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Unsubscribe a person
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
encharge_upsert_personWRITE: create a person, or update the one that already has this email, userId or Encharge id.No findings
Why it is in this group
- The name "encharge_upsert_person" says "upsert": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Create or update a person
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true

Changes things 1Creates or changes something that can be changed back.Claude Code: ask

encharge_add_tagsWRITE: add one or more tags to an existing person.No findings
Why it is in this group
- The name "encharge_add_tags" says "add": a word for a change.
Description, as the server wrote it
WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags.
Annotations the server declares
- title: Add tags to a person
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true

Only reads 5Looks things up and changes nothing.Claude Code: allow

encharge_get_accountThe Encharge account behind the API key: account id, name, site, status, timezone, people count and active services.No findings
Why it is in this group
- The name "encharge_get_account" says "get": a word for reading.
Description, as the server wrote it
The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info.
Annotations the server declares
- title: Get account
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_get_peopleLook up people (contacts) by email, userId or Encharge id.No findings
Why it is in this group
- The name "encharge_get_people" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Get people
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_list_fieldsList all person fields (built-in and custom) with name, title, type and whether the field is read-only.No findings
Why it is in this group
- The name "encharge_list_fields" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List person fields
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_list_segment_peoplePeople in one dynamic segment, with paging (limit/offset), optional sort and a choice of person fields (attributes).No findings
Why it is in this group
- The name "encharge_list_segment_people" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List people in a segment
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
encharge_list_segmentsList the dynamic segments of the account with id, name and conditions.No findings
Why it is in this group
- The name "encharge_list_segments" says "list": a word for reading.
Description, as the server wrote it
List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments.
Annotations the server declares
- title: List segments
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.3.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http encharge https://encharge.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__encharge__encharge_get_account",
      "mcp__encharge__encharge_get_people",
      "mcp__encharge__encharge_list_segment_people",
      "mcp__encharge__encharge_list_segments",
      "mcp__encharge__encharge_list_fields"
    ],
    "ask": [
      "mcp__encharge__encharge_add_tags"
    ],
    "deny": [
      "mcp__encharge__encharge_upsert_person",
      "mcp__encharge__encharge_unsubscribe_person",
      "mcp__encharge__encharge_remove_tags",
      "mcp__encharge__encharge_track_event"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as encharge. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/encharge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing