Integration

Encharge integration

Encharge is a marketing automation and email platform. Create or update people (contacts), look them up by email, userId or Encharge ID, list every person or the people of a dynamic segment, add and remove tags on a person and manage the account's tag list, unsubscribe, archive or GDPR-delete people, manage custom person fields, read custom object types and create, list, read or delete their records (companies and custom objects), read account information, and subscribe webhooks to Encharge events. Not included: email template editing, broadcasts, segment editing, folders, sending-domain settings, custom object schema editing and associations, and the separate Ingest and Transactional Email APIs. Authentication: either your account API key (sent in the X-Encharge-Token header, found under Account, Info in the Encharge app) or OAuth 2 (authorization code), for which Encharge issues the client credentials on request.

Connect Encharge How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Encharge.Built from the 26 Encharge tools below, on the connection you add once.

What you can do with Encharge

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Field, 4 operations

create_fieldsCreate fieldsPOSTCreates one or more custom person fields. Each needs name (the key) and type; title, format, readOnly, array, tooltip, icon and enum values are optional. Returns the created fields.
delete_fieldDelete fieldDELETEDeletes a custom person field by its name.
list_fieldsList fieldsGETLists every person field of the account (built-in and custom): name (the key to use in person objects), title, type, format and whether it is read-only or an array.
update_fieldUpdate fieldPATCHModifies a person field. name and type are required: read the field with list_fields first and send them back with your change.

Object, 4 operations

create_objectsCreate objectsPOSTCreates records of a custom object type (for example companies). Send a JSON array of objects whose keys are the type's field names (see get_object_type), with an optional externalId of your own. Returns the created records.
delete_objectDelete objectDELETEDeletes one record of a custom object type by its Encharge id.
get_objectGet objectGETReturns one record of a custom object type (for example a company) by its Encharge id.
list_objectsList objectsGETLists the records of a custom object type (for example companies), page by page (limit and offset), optionally with chosen fields and a sort order. The fields of each record are the ones get_object_type lists.

Person, 4 operations

archive_personArchive personDELETEArchives a person (the preferred removal); with force=true deletes the person and all their data instead (GDPR), which cannot be undone. Identify it by email, userId or Encharge ID.
get_personGet personGETLooks up one person by email, userId or Encharge ID and returns its fields (users array). Pass one of the three identifiers; archived people are left out unless includeArchived is true.
list_segment_peopleList segment peopleGETLists the people in a segment, page by page (limit and offset), optionally with chosen person fields and a sort order.
upsert_peopleUpsert peoplePOSTCreates or updates people: each person is matched by id, userId or email and updated if found, else created. Send a JSON array of person objects; returns the people as stored.

Tags management, 3 operations

create_tagsCreate tagsPOSTCreates tags in the account's tag list (without tagging anyone; add_tag tags a person). Returns the created tags.
delete_tagDelete tagDELETEDeletes a tag from the account; it is removed from every person who had it.
list_tagsList tagsGETLists the tags defined in the account, with their color, description and creation date.

Event subscription, 2 operations

create_webhookCreate webhookPOSTSubscribes a URL to an Encharge event (webhook); Encharge then POSTs endUserData (the people concerned) and eventPayload to it. Returns the id for delete_webhook. Deliveries carry no documented signature.
delete_webhookDelete webhookDELETEDeletes a webhook (event subscription) by the id returned by create_webhook.

Schema, 2 operations

get_object_typeGet object typeGETReturns one custom object type: its name, display names, description, fields and associations.
list_object_typesList object typesGETLists the custom object types of the account (companies and other custom objects): name, display names, fields, searchable fields and associations. Pass a name as objectName to the object tools.

Tag, 2 operations

add_tagAdd tagPOSTAdds one or more tags to an existing person, identified by email, userId or Encharge ID.
remove_tagRemove tagDELETERemoves one or more tags from an existing person, identified by email, userId or Encharge ID.

All, 1 operation

list_peopleList peopleGETLists every person in the account, page by page (limit and offset), optionally with chosen person fields and a sort order.

Count, 1 operation

list_tag_countsList tag countsGETLists every tag of the account with the number of people tagged with it.

Info, 1 operation

get_accountGet accountGETReturns information about the connected Encharge account: name, site, timezone, status, number of people and active services.

Segment, 1 operation

list_segmentsList segmentsGETLists the dynamic segments of the account with their id, name, color and conditions. Pass a segment id to list_segment_people.

Unsubscribe, 1 operation

unsubscribe_personUnsubscribe personPOSTUnsubscribes a person so Encharge sends them no more email. Identify them by email, userId or Encharge ID (at least one).

Use Encharge from Claude Code, Cursor or Codex

Connect Encharge in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Encharge operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Encharge

Create your workspace
Sign up free. Nothing to install.
Connect Encharge once
Add your Encharge connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.