Skip to content

Marketing Automation

iPost MCP connector

The iPost connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent add contacts, build lists, adjust journeys, and manage automations in iPost, with each person working inside their own access and every action logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect iPost to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect iPost once

  1. Open Connections, choose Add connection, and pick iPost.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste an iPost API key. One person generates a token in iPost and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

ipost
iPost
Beamer
Buffer
ClickSend
Dotdigital
Dub
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect iPost to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect iPost to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect iPost to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect iPost to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with iPost through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Marketing

    Add a new contact after a signup

    Create the iPost contact from a form fill or event badge scan, fill in the right columns, and drop them onto the welcome list in one ask.

  • Email marketing

    Build the list for the next send

    Create a fresh iPost list, add the contacts who fit, and remove anyone who should not be on it before the campaign goes out.

  • Marketing operations

    Load a batch of contacts at once

    Paste in the attendee spreadsheet from last week's webinar and have the contacts and their list memberships created in bulk instead of row by row.

  • Lifecycle

    Adjust a journey without opening the builder

    Pull up a journey automation, check how it is set up today, and change the timing or the entry conditions from a plain description.

  • Sales

    Check whether a lead is subscribed

    Ask for a contact's status in iPost before a call so you know if they are active, bounced, or unsubscribed.

  • Data

    Add a field or data table for a campaign

    Create a new column for a loyalty tier or a data table for product catalog content so the next send can personalize on it.

Try asking

  • “Which iPost lists grew most in the last 14 days”
  • “Add these 40 contacts to the iPost onboarding list”
  • “Show iPost contact status for last week's bulk create”

See all 38 iPost tools below

AI tools

iPost tools for your AI agents

38 tools are ready to call through Elaichi's MCP endpoint the moment you connect iPost, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting iPost gets you

6 screens from the product, each doing one job for your iPost account.

The agent

Ask about iPost contacts in plain language.

Type a question and get answers from live iPost contacts, lists and columns.

  • contacts
  • lists
  • list contacts
  • columns

Ask Elaichi to work across your apps.

Which iPost lists grew most in the last 14 days

Add these 40 contacts to the iPost onboarding list

Show iPost contact status for last week's bulk create

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach iPost.

One governed MCP endpoint for iPost, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

38 iPost tools land ready to call.

Browse iPost contact, list and column tools with no custom code written.

  • Create a iPost contact
  • Update a iPost contact by ID
  • Get single iPost contact by ID
  • List all iPost contacts
ElaichiTools
Tool Action Description
Create a iPost contact Create Add a contact to the iPost account. GlobalEmailStatus and GlobalMobileStatus are assumed true when their corresponding Email or Mobile fields are present, and ignored when those fields are absent. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus.
Update a iPost contact by ID Update Update an iPost contact's information by ContactID. GlobalEmailStatus and GlobalMobileStatus are assumed true when their corresponding Email or Mobile fields are present, and ignored when those fields are absent. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus. Required: id.
Get single iPost contact by ID Get Retrieve an iPost contact using the blob — an encrypted tracking token optionally appended to tracked links in iPost mailings. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus. Required: id (blob value).
List all iPost contacts List List contacts on a specific iPost list by list ID. Returns up to 10,000 contact records per call. Returns: Contact_ID, Email, Mobile, GlobalEmailStatus, GlobalMobileStatus. Required: list_id.
IPost contacts bulk create Create Add multiple contacts to an iPost journey automation. Each recipient can be identified by an existing Contact_ID or by Email (which may create a new contact if no match is found). An optional Properties object supplies iTL template variable values for journey email assembly, overriding matching contact profile fields. Returns an opaque confirmation response from the journey automation endpoint. Required: journey_id, Recipients.

Toolboxes

Every team gets its own iPost toolbox.

Scope curated iPost toolboxes to lifecycle, campaigns, support and data teams separately.

  • Lifecycle marketing
  • Campaign operations
  • Data operations
  • Customer support
ElaichiToolboxes
Name Source template Tools Created

Lifecycle marketing toolbox

iPost · contacts and list membership

iPost starter 18 Mar 4, 2026

Campaign operations toolbox

iPost · lists and sends

9 Mar 2, 2026

Data operations toolbox

iPost · bulk contact imports

24 Feb 27, 2026

Customer support toolbox

iPost · contact status lookups

iPost starter 6 Feb 19, 2026

Analytics toolbox

iPost · list and contact reporting

31 Jan 30, 2026

CRM administration toolbox

iPost · columns and field mapping

12 Jan 22, 2026

Shared connections

Share iPost accounts, never the credential.

See who connected each iPost account and which teams and members use it.

  • Lifecycle EMEA
  • Campaign ops
  • Data operations
  • Support
ElaichiConnections
Connection Scope Status Access
IP

iPost (Lifecycle EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
IP

iPost (Campaign ops)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
IP

iPost (Data operations)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
IP

iPost (Support)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
IP

iPost (Analytics)

Connected by Clara Nowak

Personal • Active Not shared
IP

iPost (Partner marketing)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which iPost contact.

Every iPost call is logged with time, actor, action, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

iPost Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

iPost Contacts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

iPost Contacts List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your iPost digest.

Six steps fetch and group iPost contacts, draft a digest, then post approved.

iPost digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch contacts

    iPost

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    iPost

    Queued

Collections and dashboards

iPost list health, refreshed on schedule.

Four metrics, 14 days of iPost contacts created, split by team, computed directly.

iPost health

Refreshed 4 minutes ago · every 15 minutes · from the contacts collection

Live

Contacts

1,284 ↓ 12%

Lists

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Contacts created

Last 14 days

By team

Share of activity

Lifecycle EMEA 34%

Campaign ops 27%

Data operations 21%

Support 18%

FAQ

Frequently asked questions

How do I connect iPost to Claude?

Connect iPost in Elaichi first by pasting the API key from your iPost account. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in iPost and no client ID or secret to generate, so the whole thing takes a few minutes.

Does iPost work with ChatGPT and Cursor as well as Claude?

Yes. Once iPost is connected in Elaichi, the same https://api.elaichi.ai/mcp endpoint works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect iPost once and every client picks it up.

What can an AI agent actually do with my iPost data?

An agent can create and update contacts, look up a single contact or a contact's subscription status, and load a batch of contacts or list memberships in one go. It can create, rename, and delete lists, add columns, and create, review, or change journey and process automations and data tables in iPost. Because iPost has a large set of actions, short concrete asks like "add these ten people to the spring list" work better than long paragraphs.

Does connecting iPost give the AI my whole account?

The AI can only reach what the iPost API key you connected can reach, and every person signs in to Elaichi as themselves so their actions are their own. Elaichi can narrow that access further by team or by action, and it can never widen it beyond what iPost already allows.

Can my team share one iPost connection?

Yes. One person connects iPost in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every iPost change, not the shared connection.

Can I stop an agent from deleting or changing things in iPost?

Yes. Restrictions in Elaichi work per action, so you can allow creating contacts and lists while blocking deleting lists, columns, or process automations in iPost. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it.

What happens to an iPost connection when someone leaves?

Offboarding a person in Elaichi ends their access to iPost through every client at once. If they connected a shared iPost account, that connection keeps working for everyone else on the team. Disconnecting iPost once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put iPost in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.