How do AI agents use Cyberimpact through Open Connector?

Your user connects Cyberimpact once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Cyberimpact tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Cyberimpact MCP server?

Yes. Open Connector can serve Cyberimpact as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Cyberimpact actions with credentials injected server-side.

Where do Cyberimpact credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Cyberimpact integration

Cyberimpact integration for AI agents.

Cyberimpact integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Cyberimpact tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Cyberimpact actions, managed and audited.

Your user connects Cyberimpact once; your agent can then use Cyberimpact API to manage email marketing members, groups, consent, mailings, and related account resources — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Cyberimpact access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Cyberimpact tools.

51 tools are generated from the published Cyberimpact catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 51 tools. All published catalog entries are included in this page's server-rendered HTML.

Add groups to member: Make the specified member part of the specified groups.; Members
Add a batch: Submit a batch for processing. Batches can be of three types: **addMembers**, **unsubscribe**, and **deleteMembers**. ### Batch type: unsubscribe Provide a list of member IDs (integer) or email addresses (string) to unsubscribe. ### Batch type: deleteMembers Provide a list of member IDs (integer) or email addresses (string) to delete. ### Batch type: addMembers Add or update members in bulk. Key behaviors: - If a member already exists, it is updated with the provided information. - If a field is empty and data already exists for that field, the existing data is kept. - To explicitly clear a field, use the special string `__EMPTY__`. - All submitted members will be added to the specified groups (in addition to any existing group memberships). - The `relationType` field is required and accepts: `express-consent`, `active-clients`, `information-request`, `business-card`, `web-contacts`, `purchased-list`, `contest-participants`, `mixed-list`, `inactive-clients`, `association-members`, `employees`, `partners`.; Batches
Add a new group: Add a new static group in your account.; Groups
Create a new mailing: Create a new mailing scheduled to be sent.; Mailings
Add a new member: Add a new member in your account. If you need the member to confirm their subscription, it is recommended that you use the opt-in endpoint instead. If you use this method in an online form, it is **strongly recommended** to add a CAPTCHA to avoid abuse. Warning: This method is throttled. If you wish to use it for synchronization purposes between two systems, please contact us. If you need to add multiple members at once, use the batches endpoint.; Members
Create template: Create a new template.; Templates
Delete a group: Delete a specific group based on its ID.; Groups
Delete a mailing: Delete a specific mailing based on its ID (only if it has not already been sent).; Mailings
Delete a member: Delete a specific member based on their key.; Members
Delete a template: Delete a specific template based on its ID.; Templates
Edit a group: Modify the representation of a group by changing only the specified attributes. Unspecified attributes are left untouched. Note: Editing a dynamic group is not possible from the API.; Groups
Edit a member: Modify the representation of a member by changing only the specified attributes. Unspecified attributes are left untouched.; Members
Generate an API token: Generate a token that will be associated to your account and be used to call this API.; Tokens
Retrieve archived mailings: Retrieve a paginated list of archived mailings.; Mailings
Retrieve a batch: Retrieve a specific batch based on its ID. This is useful to check whether a batch has finished processing and to get the results. Some requests in the batch may have succeeded while others failed. The `result` field provides the details.; Batches
Retrieve bounced members: Retrieve a paginated list of members for which a hard bounce was received for the last mailing sent to them.; Members
Retrieve account custom fields list: List of custom fields set in your account. Field type can be one of: - text - date - integer - decimal number; Members
Retrieve group: Retrieve a specific group based on its ID.; Groups
Retrieve group members: Retrieve a paginated list of all the members in the specified group.; Groups
Retrieve groups: Retrieve a paginated list of groups.; Groups
Retrieve a mailing: Retrieve a specific mailing based on its ID.; Mailings
Retrieve recipients of the mailing: Retrieve a paginated list of a mailing's recipients.; Mailings
Retrieve recipients which have clicked in the mailing: Retrieve a paginated list of a mailing's recipients which have clicked at least one link in the mailing.; Mailings
Retrieve recipients to which the mailing was successfully delivered: Retrieve a paginated list of recipients to which the mailing was successfully delivered.; Mailings
Retrieve recipients which have hard bounced: Retrieve a paginated list of a mailing's recipients which have hard bounced.; Mailings
Retrieve recipients which have opened the mailing: Retrieve a paginated list of a mailing's recipients which have opened the mailing.; Mailings
Retrieve recipients which have soft bounced: Retrieve a paginated list of a mailing's recipients which have soft bounced.; Mailings
Retrieve recipients for which the mailing was not sent because it was stopped: Retrieve a paginated list of recipients for which the mailing was not sent because it was stopped. If the mailing was not stopped, this will return an empty list.; Mailings
Retrieve recipients which have unsubscribed from a mailing: Retrieve a paginated list of a mailing's recipients which unsubscribed by using the unsubscribe link in the mailing.; Mailings
Retrieve a specific member: Retrieve a specific member based on their key.; Members
Retrieve a specific member's consent details: Retrieve more consent information for a specific member based on their key.; Members
Retrieve member's groups: Retrieve a paginated list of the groups that the specified member is part of.; Members
Retrieve member's received mailings: Retrieve a paginated list of the member's received mailings.; Members
Retrieve members: Retrieve a paginated list of your members. Active members are subscribed members that are part of group(s). Orphan members are subscribed members that are not part of a group. Note: The returned property `items_per_page` is deprecated and will eventually be removed. Use `limit` instead.; Members
Ping: Simple function to verify your connection with the API.; General
Retrieve scheduled mailings: Retrieve a paginated list of all scheduled mailings.; Mailings
Retrieve sent mailings: Retrieve a paginated list of all sent mailings. Note: This does not include any archived mailings.; Mailings
Retrieve a template: Retrieve a specific template based on its ID.; Templates
Retrieve templates: Retrieve a paginated list of the templates.; Templates
Retrieve a specific unsubscribed member: Retrieve a specific unsubscribed member based on their email address.; Members
Retrieve unsubscribed members: Retrieve a paginated list of members who unsubscribed from your mailings.; Members
Opt-in a member: Send an opt-in email to the specified email address, creating the member if not already existing and adding them to the specified list of groups. Warning: This method is throttled. If you use it in an online form, it is **strongly recommended** to add a CAPTCHA to avoid abuse.; Members
Remove all members from group: Remove all members from a specific group.; Groups
Remove member from a group: Remove the specified member from the specified group.; Members
Replace a group: Modify the representation of a group so that it becomes completely as specified. Unspecified attributes will be reset to their default empty values. Note: Replacing a dynamic group is not possible from the API.; Groups
Replace a member: Modify the representation of a member so that it becomes completely as specified. Unspecified attributes will be reset to their default empty values.; Members
Replace member's groups: Replace completely the list of groups that a member is part of with the ones specified.; Members
Replace a template: Modify the representation of a template so that it becomes completely as specified. Unspecified attributes will be reset to their default empty values.; Templates
Revoke an API token: Permanently revoke the API token identified by `tokenUniqueId`. Once revoked, the token can no longer be used to authenticate API requests.; Tokens
Set consent for a specific member: Set consent for a specific member based on their key. Note: Some consent types cannot be overridden — this method returns a 422 status code with a message when that happens.; Members
Unsubscribe a member: Unsubscribe a member based on their key. The field `isNewUnsubscription` indicates whether the unsubscription was new or the member was already unsubscribed.; Members

FAQ

Cyberimpact integration, answered

How do AI agents use Cyberimpact through Open Connector?: Your user connects Cyberimpact once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Cyberimpact tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Cyberimpact MCP server?: Yes. Open Connector can serve Cyberimpact as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Cyberimpact actions with credentials injected server-side.
Where do Cyberimpact credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Cyberimpact — keep the keys.

Open source, self-hostable, with Cyberimpact credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →