PlainFunnels Categories

Home / Categories / MCP

What can an AI actually do inside my systeme.io account?

Short answer

systeme.io documents nine groups of tools. Contacts, tags, products and price plans are fully covered, but a funnel can be created and not edited, and an automation rule can only use three triggers.

The documented list

systeme.io groups the MCP server's tools into nine areas. The right-hand column is the part worth reading.

GroupWhat it can doWhat it cannot
Contacts, tags, contact fieldsCreate, update, delete, list and retrieve contacts. Create, update, delete, assign, list and remove tags. List contact fields and their slugsNothing documented as missing
Newsletters and email campaignsCreate a newsletter in the classic or visual editor, update its subject line, preview text and content, send a test, schedule it or send it. Create, retrieve, update and delete campaigns and individual campaign stepsDelete a newsletter. Change the sender name or address. Schedule or activate a campaign step
FunnelsCreate a funnel, create an opt-in step, list and retrieve bothEdit or delete a funnel or a step. Handle any step type other than opt-in
Price plans and couponsCreate, edit, list and delete bothChange a coupon's discount amount or percentage after it exists
Automation rulesCreate a rule from three triggers, and list existing rulesEdit or delete a rule
Digital productsCreate, view, update, delete, list, and link a price planNothing documented as missing
Physical productsCreate, view, update, delete, and connect to order forms, upsells and downsellsNothing documented as missing
Offers and sales settingsCreate and configure offers for order forms, upsells and downsells, covering coupons, order bumps, currency, payment methods, tax settings, affiliate commissions, payout delays and sales limits, with products attachedNothing documented as missing
SMS templates and booking calendar eventsList and searchEverything else

The three automation triggers

Automation rules are the narrowest group, and the numbers are worth having in front of you before asking for one.

  • Triggers: Tag added, Tag removed, Funnel form subscribed.
  • Actions: Add a tag, Remove a tag.

Anything outside those five pieces is not supported through the MCP server.

What that means in practice

The pattern across the whole surface is that creating is well covered and undoing is not.

A funnel made through the chat window cannot be renamed or removed through it. An automation rule made that way is permanent as far as the server is concerned. A newsletter can be written, scheduled and sent through the server but cannot be deleted through it.

systeme.io marks these as current limitations and says more will be added over time.

The two documents do not agree

systeme.io's developer documentation lists a much smaller surface than its help centre.

The developer page says the server supports contacts, tags, tag assignment, contact fields and newsletters, and states plainly that at this stage these are the only capabilities exposed. It carries an "Updated 3 months ago" stamp.

The help centre lists all nine groups above, and six of them have a dedicated article of their own working through the prompts. Those articles are much the more detailed of the two accounts.

What actually runs out first

Requests. The MCP server follows the same rate limiting as the systeme.io public API, with a ceiling per time window and a quota that refills at intervals.

The quota is shared across all your MCP keys rather than allotted per key, and passing the ceiling returns a 429 Too Many Requests response.

Did this answer your question?