MCP tool reference · #466 of 563 by publishers
delete_contact
Exposed by 8 servers from 8 publishers, read from the live servers by the Serverdex check; most of them sit in Communication; 37.5% of them take a contactId parameter; the most-starred is ai.sendraven MCP (1 stars).
delete_contact(contactId: string, id: string, …)Parameters
share = % of the 8 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| contactId | string | 37.5% | 100% | CRM contact id from list_contacts |
| id | string | 37.5% | 100% | Contact id |
| audience_id | string | 12.5% | 100% | — |
| confirm | boolean | 12.5% | 100% | Must be true. Only set after the user explicitly asked for this deletion. |
| confirmation_token | string | 12.5% | 0% | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| contact_id | string | 12.5% | 100% | The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. find_contact returns the id for an address. |
| id_or_email | string | 12.5% | 100% | The contact id or its (URL-encoded) email address. |
| purge | boolean | 12.5% | 0% | true to erase the contact for good, as a data-protection erasure does (owners only); omit to take the contact and its chats out of lists and the Inbox, with its |
Source: the input schema each server returns for delete_contact, aggregated over the 8 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with delete_contact
8 of 8 · 8 publishers · 8 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes delete_contact |
|---|---|---|---|---|---|---|
| 1 | ai.sendraven MCPcommonninja · Communication | commonninja | Communication | 1 | yes | Remove a person from the workspace entirely, along with every audience membership. Their suppression and topic preferences are kept on purpose — an opt-out has to outlive the contact record, or the next import silently puts them back on the list. remove_from_audience takes someone off a single audience instead. |
| 2 | TourProtourproapp · Other | tourproapp | Other | — | yes | Permanently delete a contact. Only after the user asked for it; set confirm to true. |
| 3 | Cosendcosendhq · Communication | cosendhq | Communication | — | yes | Deletes one contact, named by id. Without purge the contact and its chats drop out of lists, counts and the Inbox, and Cosend keeps their messages until a purge; if the person writes again, they become a new contact with a new chat. With purge true the contact and what Cosend holds about them are erased for good (an owner’s action, for a data-protection request). The deletion stays inside Cosend, |
| 4 | Przypominamy.com SMSpawelmamcarz · Communication | pawelmamcarz | Communication | — | yes | Delete contact Remove a contact from the address book. Does not block the number; use add_to_blacklist for opt-out. |
| 5 | workload.zerogetitdone-gmbh · Business & CRM | getitdone-gmbh | Business & CRM | — | yes | Delete a CRM contact. Before deleting for GDPR reasons, add the address to the suppression list. |
| 6 | SpacePost404-studio · Communication | 404-studio | Communication | — | yes | Delete a contact. Requires a `full_access` API key. API: `DELETE /audiences/{audienceId}/contacts/{idOrEmail}` (operationId `deleteContact`, Contacts). |
| 7 | TextKittextkithq · Communication | textkithq | Communication | — | yes | Delete a contact. Messages, consent records, and topic preferences for the number are kept. |
| 8 | FavCRMfavcrm · Business & CRM | favcrm | Business & CRM | — | yes | Delete a secondary contact. Primary contacts are protected; set another primary contact or delete the account instead. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.