Read Cyberimpact members, groups and mailing results; add members, send opt-ins, create mailings. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"cyberimpact": {
"url": "https://cyberimpact.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"cyberimpact": {
"type": "http",
"url": "https://cyberimpact.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Cyberimpact API token.
In Cyberimpact open Developers → API tokens and create a token (a long text with two dots in it). It acts with your account's rights and can be revoked there at any time. Your token is used only to call the Cyberimpact API on your behalf; it is never shown to anyone. This is a token for integrations, not your Cyberimpact password.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Cyberimpact API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Cyberimpact connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
cyberimpact_get_account | read | Get account Check the connection and show which Cyberimpact account the API token belongs to (username, email, account name). GET /ping. |
cyberimpact_list_members | read | List members List subscribed contacts (members) with name, email, language, consent type, mailing counts and custom fields. status: active (in at least one group, default), orphans (in no group) or all. Filter by the date a member joined or was last updated. Bounced and unsubscribed members have their own tools. GET /members. |
cyberimpact_get_member | read | Get member One member by email address or id: all attributes, consent type, mailings received/opened/clicked and custom fields (keyed by custom field id; see cyberimpact_list_custom_fields). GET /members/{key}. |
cyberimpact_get_member_groups | read | Get member's groups The groups a member belongs to (id, title, public/private, dynamic). GET /members/{key}/groups. |
cyberimpact_get_member_mailings | read | Get member's mailings The mailings a member received (use it to see what a contact was sent and when). GET /members/{key}/mailings. |
cyberimpact_get_member_consent | read | Get member consent A member's consent record: consent type, relation type, consent date, expiration and proof (for CASL compliance checks). GET /members/{key}/consent. |
cyberimpact_list_bounced_members | read | List bounced members Members whose last mailing hard-bounced (invalid addresses to clean up), with the bounce date. GET /members/bounced. |
cyberimpact_list_unsubscribed_members | read | List unsubscribed members Members who unsubscribed, with the unsubscribe date. These contacts must not be mailed again. GET /members/unsubscribed. |
cyberimpact_list_custom_fields | read | List custom fields The account's custom member fields (id, name, type text/date/integer/decimal). Member customFields are keyed by these ids. GET /customfields. |
cyberimpact_list_groups | read | List groups List the account's groups (mailing lists) with member and mailing counts, public/private and dynamic flags. Use the ids to target mailings and opt-ins. GET /groups. |
cyberimpact_get_group | read | Get group One group by id with its member count, mailing count and flags. GET /groups/{id}. |
cyberimpact_list_group_members | read | List group members The members of one group, with the same member filters as cyberimpact_list_members. GET /groups/{id}/members. |
cyberimpact_list_mailings | read | List mailings List mailings by state: sent (default, archived ones excluded), scheduled (queued to go out) or archived. Each has id, subject, language, send/schedule date, recipient count and sender. Optionally only mailings sent to one group. GET /mailings/{sent|scheduled|archived}. |
cyberimpact_get_mailing | read | Get mailing One mailing by id with its results: sent/delivered/stopped counts, views, clicks, delivery/click/view rates, per-link clicks, recipient groups, sender and body (HTML/text, cut at 20 000 characters). GET /mailings/{id}. |
cyberimpact_list_mailing_recipients | read | List mailing recipients Who received a mailing and what happened: kind = all, delivered, stopped, hard_bounced, soft_bounced, unsubscribed, opened or clicked. Optionally only recipients from one group. GET /mailings/{id}/recipients[/{kind}]. |
cyberimpact_list_templates | read | List templates List the account's email templates (id, title, created/updated). GET /templates. |
cyberimpact_get_template | read | Get template One template by id with its HTML and text body (cut at 20 000 characters). GET /templates/{id}. |
cyberimpact_get_batch | read | Get batch Status of a bulk batch job (NEW, PROCESSING or COMPLETED) and its result. Set show_error_details to list the per-member errors. GET /batches/{id}. |
cyberimpact_add_member | write | Add member WRITE: add a contact as a subscribed member WITHOUT a confirmation email (implied consent) and put it in the given groups; the contact can then be mailed. Only use it for people who really gave their consent (CASL); to ask the person to confirm first use cyberimpact_send_optin. A member that already exists is rejected by the API. Throttled by Cyberimpact; for many contacts use the app's import. POST /members. |
cyberimpact_update_member | write | Update member WRITE: change only the given attributes of a member (other attributes stay as they are). The old values of the changed fields are overwritten and not recoverable through the API. Set new_email to change the address. PATCH /members/{key}. |
cyberimpact_add_member_to_groups | write | Add member to groups WRITE: add an existing member to more groups (existing group memberships are kept). Being in a group makes the member a recipient of mailings sent to it. Returns the member's groups after the update. POST /members/{key}/groups. |
cyberimpact_send_optin | write | Send opt-in email WRITE, SENDS AN EMAIL to the given address: an opt-in confirmation request. The person is added to the groups only after they confirm (the member is created if it does not exist). Use this instead of cyberimpact_add_member when you do not have the person's consent yet. Only call it after the user has approved sending to this address, and set confirm_send to true. Throttled by Cyberimpact. POST /members/optins. |
cyberimpact_create_group | write | Create group WRITE: create a new, empty group (mailing list). A public group can be offered on subscription forms; a private one is internal. Groups cannot be deleted through this server. POST /groups. |
cyberimpact_create_template | write | Create template WRITE: create a new email template from HTML and/or text. It is only saved in the account; nothing is sent. POST /templates. |
cyberimpact_create_mailing | write | Schedule mailing WRITE, SENDS EMAIL TO CUSTOMERS: create a mailing scheduled to be sent at send_at to every member of the chosen groups. It goes out for real unless it is cancelled in the Cyberimpact app before send_at. Only call it after the user has approved the subject, body, sender and groups, and set confirm_send to true. mail_from must be a validated sender address of the account. A mailing cannot be deleted through this server. POST /mailings. |
cyberimpact_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
cyberimpact_request_feature | Request a missing feature Tell usefulapi that the user needs something the Cyberimpact tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
cyberimpact_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Cyberimpact (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
cyberimpact_cancel_subscription | Cancel the Pro subscription Cancel the caller's Cyberimpact Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run cyberimpact_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Cyberimpact server only. Subscribe with cyberimpact_upgrade (it returns a Stripe Checkout link). Cancel any time with cyberimpact_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running cyberimpact_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Cyberimpact. The server calls the Cyberimpact API with your own Cyberimpact access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Cyberimpact API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Cyberimpact API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Cyberimpact API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Cyberimpact.
Yes, if you approve it. 7 of the 25 Cyberimpact tools can create or change data. The other 18 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Cyberimpact server only. Cancel any time: Pro then runs to the end of the paid period. Run cyberimpact_usage_status to see how many calls you used.
Ask the AI to run cyberimpact_upgrade: it returns a Stripe Checkout link. To cancel, run cyberimpact_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with cyberimpact_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.