Encharge MCP by usefulapi

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

我该使用它吗

质量与安全性

B
描述质量
96%
模式完整度
77%
命名质量
80%
投毒风险
80%
权限匹配度
100%
协议合规性
100%

发现(2)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domain在 encharge_track_event 中

基于对工具定义和协议合规性的自动分析。

上下文开销

~2,281token 数(工具定义)
~1.7 KB典型响应大小
对注意力有中等影响(占 128k 上下文窗口的 1.78%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

{
  "mcpServers": {
    "encharge": {
      "url": "https://encharge.usefulapi.io/mcp"
    }
  }
}

远程端点

https://encharge.usefulapi.io/mcpstreamable-http

它能做什么

工具清单

工具(10)

🟢 只读🟡 写入🔴 删除⚪ 未知
🟢encharge_get_account

The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info.

输入模式

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢encharge_get_people(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.

输入模式

{
  "type": "object",
  "properties": {
    "people": {
      "minItems": 1,
      "maxItems": 20,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "email": {
            "type": "string",
            "minLength": 3,
            "maxLength": 320,
            "format": "includes",
            "pattern": "@",
            "description": "Email address of the person."
          },
          "userId": {
            "type": "string",
            "minLength": 1,
            "maxLength": 200,
            "description": "The userId your own app uses for the person."
          },
          "id": {
            "type": "string",
            "minLength": 1,
            "maxLength": 100,
            "description": "Encharge id of the person (a UUID)."
          }
        }
      },
      "description": "People to look up, each with at least one of email, userId or id."
    }
  },
  "required": [
    "people"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢encharge_list_segment_people(segment_id, limit, offset, attributes, sort, ...)

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.

输入模式

{
  "type": "object",
  "properties": {
    "segment_id": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991,
      "description": "Encharge segment id (from encharge_list_segments)."
    },
    "limit": {
      "description": "People per page, 1-100 (default 25).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 100
    },
    "offset": {
      "description": "Number of people to skip (default 0). Pass the previous reply's next_offset.",
      "type": "integer",
      "minimum": 0,
      "maximum": 1000000
    },
    "attributes": {
      "description": "Person field names to return. Default: the standard fields.",
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      }
    },
    "sort": {
      "description": "Person field name to sort by.",
      "type": "string",
      "minLength": 1,
      "maxLength": 100
    },
    "order": {
      "description": "Sort order (default asc).",
      "type": "string",
      "enum": [
        "asc",
        "desc"
      ]
    }
  },
  "required": [
    "segment_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴encharge_upsert_person(email, userId, id, firstName, lastName, ...)

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.

输入模式

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "minLength": 3,
      "maxLength": 320,
      "format": "includes",
      "pattern": "@",
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "The userId your own app uses for the person."
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "Encharge id of the person (a UUID)."
    },
    "firstName": {
      "description": "First name.",
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "lastName": {
      "description": "Last name.",
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "fields": {
      "type": "object",
      "propertyNames": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      },
      "additionalProperties": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 10000
          },
          {
            "type": "number"
          },
          {
            "type": "boolean"
          },
          {
            "type": "null"
          }
        ]
      },
      "description": "Other person fields by field name (see encharge_list_fields), for example { \"company\": \"Acme\", \"plan\": \"pro\" }. Dates as ISO 8601."
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴encharge_unsubscribe_person(email, userId, id)

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.

输入模式

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "minLength": 3,
      "maxLength": 320,
      "format": "includes",
      "pattern": "@",
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "The userId your own app uses for the person."
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "Encharge id of the person (a UUID)."
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡encharge_add_tags(email, userId, id, tags)

WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags.

输入模式

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "minLength": 3,
      "maxLength": 320,
      "format": "includes",
      "pattern": "@",
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "The userId your own app uses for the person."
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "Encharge id of the person (a UUID)."
    },
    "tags": {
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      },
      "description": "Tag names. A tag name cannot contain a comma."
    }
  },
  "required": [
    "tags"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴encharge_remove_tags(email, userId, id, tags)

WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags.

输入模式

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "minLength": 3,
      "maxLength": 320,
      "format": "includes",
      "pattern": "@",
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "The userId your own app uses for the person."
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "Encharge id of the person (a UUID)."
    },
    "tags": {
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      },
      "description": "Tag names. A tag name cannot contain a comma."
    }
  },
  "required": [
    "tags"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢encharge_list_segments

List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments.

输入模式

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢encharge_list_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.

输入模式

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴encharge_track_event(name, email, userId, user_fields, tags, ...)

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/.

输入模式

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "Event name."
    },
    "email": {
      "type": "string",
      "minLength": 3,
      "maxLength": 320,
      "format": "includes",
      "pattern": "@",
      "description": "Email address of the person."
    },
    "userId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "The userId your own app uses for the person."
    },
    "user_fields": {
      "description": "Person fields to set on this person, by field name.",
      "type": "object",
      "propertyNames": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      },
      "additionalProperties": {
        "anyOf": [
          {
            "type": "string",
            "maxLength": 10000
          },
          {
            "type": "number"
          },
          {
            "type": "boolean"
          },
          {
            "type": "null"
          }
        ]
      }
    },
    "tags": {
      "description": "Tags to add to the person.",
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      }
    },
    "properties": {
      "description": "Properties of the event; values may be nested objects, for example { \"plan\": \"Premium\", \"trial\": { \"length\": 14 } }. Dates as ISO 8601.",
      "type": "object",
      "propertyNames": {
        "type": "string",
        "minLength": 1,
        "maxLength": 100
      },
      "additionalProperties": {}
    }
  },
  "required": [
    "name"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

社区

评价此服务器

证据

最近观测

已验证未记录版本10 个工具