Community Gmail server with auto-auth: search, read and send email via MCP.
Laposta 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.
What it does
Read Laposta lists, members, campaigns and reports; add members and build campaigns.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http laposta-mcp-by-usefulapi https://laposta.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# laposta_list_lists, laposta_get_list, laposta_list_fields and 15 more
Laposta 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.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 laposta-mcp-by-usefulapi https://laposta.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
18 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.
List all mailing lists of the Laposta account with member counts (active, unsubscribed, cleaned). Use the list_id in the other tools.
No parameter schema on file.
Get one mailing list: name, state, notification addresses and member counts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
List the custom fields of a mailing list (name, custom_name used as the key in custom_fields, datatype, required, options). Call this before adding or updating a member.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
List the segments of a mailing list (a segment id can be a campaign recipient together with its list).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
List the members (subscribers) of a mailing list, one page at a time. Filter by state, free-text search (email and field values) or label. Contains personal data: only fetch what the task needs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
| state | string | no | Only members in this state (default: all). |
| search | string | no | Only members containing this text in the email or any text/number/choice field. |
| label | string | no | Only members with this label (by name). |
| order_by | string | no | email, signup_date, or a text field's custom_name (comma-separated for several). |
| order | string | no | Sort direction for order_by (default asc). |
| limit | integer | no | Items per page (default 25, max 100; a large page can be cut at 50,000 characters and lose its next_cursor). |
| cursor | string | no | Cursor: pass the previous reply's next_cursor unchanged, with the same filters. |
Get one member of a list by member id or email address: state, signup/confirm dates and custom field values.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
| member | string | yes | The member id OR the member's email address. |
The event history of one member (subscribed, confirmed, opened, clicked, bounced, unsubscribed, automations ...), newest first by default. Optionally limited to one campaign or a date range. Paged by cursor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
| member | string | yes | The member id OR the member's email address. |
| campaign_id | string | no | Only events of this campaign. |
| event_date_from | string | no | Events from this moment, inclusive. |
| event_date_to | string | no | Events before this moment, exclusive. |
| order | string | no | Sort by event date (default desc). |
| limit | integer | no | Items per page (default 25, max 100; a large page can be cut at 50,000 characters and lose its next_cursor). |
| cursor | string | no | Cursor: pass the previous reply's next_cursor unchanged, with the same filters. |
List the account's campaigns (name, subject, sender, recipient lists, delivery moments). Use limit/offset to page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Items to return (default 100, max 500). |
| offset | integer | no | Items to skip (default 0). Pass the previous reply's next_offset. |
Get one campaign: name, subject, preview text, sender, reply-to, recipients, delivery moments and web version URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
Get the plain-text content of a campaign (and its import_url if it was imported). Set include_html to also get the full HTML (large).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| include_html | boolean | no | Also return the HTML body (default false). |
Recipient events of one campaign (delivered, opened, clicked, bounced, unsubscribed ...), newest first by default, optionally within a date range. Paged by cursor. For totals use laposta_get_report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| event_date_from | string | no | Events from this moment, inclusive. |
| event_date_to | string | no | Events before this moment, exclusive. |
| order | string | no | Sort by event date (default desc). |
| limit | integer | no | Items per page (default 25, max 100; a large page can be cut at 50,000 characters and lose its next_cursor). |
| cursor | string | no | Cursor: pass the previous reply's next_cursor unchanged, with the same filters. |
Result figures of all campaigns: sent, accepted, opened, clicked, bounced, unsubscribed, with ratios. Use limit/offset to page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Items to return (default 100, max 500). |
| offset | integer | no | Items to skip (default 0). Pass the previous reply's next_offset. |
Result figures of one campaign: sent, accepted, unique opens and clicks, bounces, complaints, unsubscribes and their ratios.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
WRITE: add one email address to a mailing list (subscribe). On a double opt-in list Laposta sends the confirmation email to that address. The address must have given consent. With upsert, an existing active member's fields are overwritten; an unsubscribed member is re-activated unless suppress_reactivation is set.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
| string | yes | — | |
| ip | string | yes | IP address the signup came from (required by Laposta; use the signup source's address, or your own server's if it was entered by staff). |
| source_url | string | no | URL the signup came from. |
| custom_fields | object | no | Custom field values keyed by the field's custom_name (the variable name shown by laposta_list_fields). Multi-choice fields take an array of option values. |
| upsert | boolean | no | Overwrite the fields if the address is already an active member (default false: error). |
| suppress_reactivation | boolean | no | With upsert: do not re-activate an unsubscribed member. |
| suppress_email_notification | boolean | no | Do not send the list's signup notification email. |
WRITE: change a member's custom field values and/or email address, or unsubscribe the member (state: unsubscribed). Only the fields you pass change. Re-subscribing a person is not offered here: do it in the Laposta app or with laposta_add_member upsert only when they asked for it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
| member | string | yes | The member id OR the member's email address. |
| string | no | A new email address for this member. | |
| state | string | no | Set to unsubscribed to unsubscribe the member. |
| custom_fields | object | no | Custom field values keyed by the field's custom_name (the variable name shown by laposta_list_fields). Multi-choice fields take an array of option values. |
WRITE: create a new regular campaign (a draft: it is NOT filled, scheduled or sent). Fill it with laposta_set_campaign_content, check it with laposta_send_test_email and send it in the Laposta app. The from_email must be an approved sender address of the account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Internal campaign name. |
| subject | string | yes | Subject line. |
| from_name | string | yes | Sender name. |
| from_email | string | yes | Sender email address (must be an approved sender in Laposta). |
| list_ids | array | yes | Recipients: list ids and optionally segment ids. |
| reply_to | string | no | Reply-to address. |
| previewtext | string | no | Preview text (max 120 characters). |
| google_analytics | boolean | no | Link Google Analytics tracking. |
WRITE: replace a campaign's content with your HTML, or let Laposta import it from a URL (html wins if both are given). Does not send anything. The reply's report lists problems Laposta found (javascript, missing unsubscribe link, missing images).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| html | string | no | The complete HTML of the email. |
| import_url | string | no | A public URL Laposta fetches the HTML from. |
| inline_css | boolean | no | Inline the CSS. |
WRITE: send a test copy of a campaign (it must have content and not be sent yet) to ONE email address. Does not send the campaign to its recipients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| string | yes | Where to send the test. |
- 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 Laposta MCP by usefulapi or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| laposta_list_lists | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_list | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_list_fields | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_list_segments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_list_members | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_member | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_member_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_list_campaigns | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_campaign | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_campaign_content | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_campaign_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_list_reports | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_get_report | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laposta_add_member | external-sink | external-sink: declares destructiveHint: true, openWorldHint: true |
| laposta_update_member | external-sink | external-sink: declares destructiveHint: true, openWorldHint: true |
| laposta_create_campaign | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| laposta_set_campaign_content | external-sink | external-sink: declares destructiveHint: true, openWorldHint: true |
| laposta_send_test_email | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.12.5.
No release note was published with this version.
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.
Any signed-in account that does not publish Laposta 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.
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.