Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Encharge MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Manage Encharge people, tags, segments and fields, and track events for email automation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http encharge-mcp-by-usefulapi https://encharge.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# encharge_get_account, encharge_get_people, encharge_list_segment_people and 7 more
Encharge MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http encharge-mcp-by-usefulapi https://encharge.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The Encharge account behind the API key: account id, name, site, status, timezone, people count and active services. GET /accounts/info.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| people | array | yes | People to look up, each with at least one of email, userId or id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| segment_id | integer | yes | Encharge segment id (from encharge_list_segments). |
| limit | integer | no | People per page, 1-100 (default 25). |
| offset | integer | no | Number of people to skip (default 0). Pass the previous reply's next_offset. |
| attributes | array | no | Person field names to return. Default: the standard fields. |
| sort | string | no | Person field name to sort by. |
| order | string | no | Sort order (default asc). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Email address of the person. | |
| userId | string | no | The userId your own app uses for the person. |
| id | string | no | Encharge id of the person (a UUID). |
| firstName | string | no | First name. |
| lastName | string | no | Last name. |
| fields | object | no | Other person fields by field name (see encharge_list_fields), for example { "company": "Acme", "plan": "pro" }. Dates as ISO 8601. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Email address of the person. | |
| userId | string | no | The userId your own app uses for the person. |
| id | string | no | Encharge id of the person (a UUID). |
WRITE: add one or more tags to an existing person. Tags that do not exist yet are created. POST /tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Email address of the person. | |
| userId | string | no | The userId your own app uses for the person. |
| id | string | no | Encharge id of the person (a UUID). |
| tags | array | yes | Tag names. A tag name cannot contain a comma. |
WRITE: remove one or more tags from an existing person. The tags themselves are not deleted. DELETE /tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Email address of the person. | |
| userId | string | no | The userId your own app uses for the person. |
| id | string | no | Encharge id of the person (a UUID). |
| tags | array | yes | Tag names. A tag name cannot contain a comma. |
List the dynamic segments of the account with id, name and conditions. Use the ids with encharge_list_segment_people. GET /segments.
No parameter schema on file.
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.
No parameter schema on file.
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Event name. |
| string | no | Email address of the person. | |
| userId | string | no | The userId your own app uses for the person. |
| user_fields | object | no | Person fields to set on this person, by field name. |
| tags | array | no | Tags to add to the person. |
| properties | object | no | Properties of the event; values may be nested objects, for example { "plan": "Premium", "trial": { "length": 14 } }. Dates as ISO 8601. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Encharge MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Encharge MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.