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

An AI can do more inside a systeme.io account than either of systeme.io's own documents says. A connection checked in a live account exposed 113 tools, 53 that only read and 60 that change something, covering contacts, funnels, page content, courses, email, products, pricing, automation and bookings.

What an AI can do in a systeme.io account

What is actually connected

A systeme.io MCP connection checked in a live account on 4 September 2026 exposed 113 tools.

Checking any of this yourself starts at your own profile picture, then Settings, then MCP & API keys. A live account confirms that screen holds two separate sections, Public API keys and, below it, MCP keys, each with its own Create button. Making the key itself is covered separately.

53 of them only read. Their names begin with get_, describe_ or search_, and they return information without touching anything. The other 60 change something.

That count is the honest answer to the question, and it is larger than either document systeme.io publishes. Both of those are quoted further down.

The fourteen areas

The tools are named after the part of the dashboard they act on, so the list maps onto the menu rather than onto anything technical.

Area	Tools	What is in it
Contacts	5	Create, read and update a contact, list contacts, and list the contact fields. No delete tool
Tags	10	Create, read and update a tag, put one on a contact or take it off, and read or set the include and exclude tags on a newsletter. No delete tool
Funnels and funnel steps	10	Create a funnel or a step, read and search both, and save page content into a funnel page
Page content and editing	6	Read a page's editable content and write content back, plus three describe_ tools that hand the AI the page schema and the editing rules
Courses, modules and lectures	21	Create, update and delete courses, modules and lectures, activate or deactivate a course or a single lecture, and read the course themes
Email campaigns	11	Create, read, update and delete a campaign and its individual steps, and send a test of one step
Newsletters	9	Create, read, update and delete a newsletter, read or set its schedule, send a test, and send it to the list
Products	10	Create, read, update and delete both digital and physical products
Price plans and offers	8	Create, read and update price plans and offers, and delete a price plan
Coupons	5	Create, read, update and delete a coupon
Automation rules	5	Create, read, update and delete a rule
Calendar and bookings	6	Create, read, update and delete a calendar event, and list booking calendar events and the bookings taken on them
Sales settings and payments	3	Read the payment methods available, read the sales settings, and update them
Account information	3	List the domains on the account, the files, and the SMS templates

Those fourteen come to 112. The last one is describe_mcp_instructions, which returns the server's own instruction text and is how the connection was confirmed live before anything was counted.

The biggest area is one nobody documents

Courses, modules and lectures, at 21 tools. That is more than contacts and tags put together, and it is the area with the fullest set of verbs: create, read, update and delete on all three levels, plus activate and deactivate on a course and on a single lecture.

Neither the developer page nor the help centre mentions courses in connection with MCP at all.

What it can delete

12 of the 113 tools remove something.

Courses: delete_course, delete_course_module, delete_lecture.
Email: delete_campaign, delete_campaign_step, delete_newsletter.
Selling: delete_digital_product, delete_physical_product, delete_price_plan, delete_coupon.
The rest: delete_automation_rule and delete_calendar_event.

Two deletions people expect are not on the list. The connection carries no tool for deleting a contact and none for deleting a tag, even though systeme.io's help centre gives the prompt for both and its developer page lists delete under Contacts and under Tags.

It carries no tool for deleting a funnel or a funnel step either. That one matches the documentation: article 11408 states that modifying or deleting funnels and funnel steps is not supported.

The three automation triggers

Automation rules are the narrowest area in what they can express, and the pieces 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.

systeme.io's own example prompt shows how the two go together: Create an automation rule that adds the tag "New Lead" when someone subscribes to the "Summer campaign" funnel form.

Anything outside those five pieces is not supported.

Where the connection goes further than the documentation

Four places, and the gap runs the same way each time. The tools exist and the documentation has not caught up.

Thing	What systeme.io publishes	What the connection exposes
Editing an automation rule	Article 11414: editing and deleting rules are not supported at this time	update_automation_rule and delete_automation_rule
Deleting a newsletter	Article 11407: it is not currently possible to delete newsletters using MCP tools	delete_newsletter
Calendar events	Article 9489: booking calendar events are list and search only	create_calendar_event, update_calendar_event, delete_calendar_event
Editing page content	Nothing. Neither document mentions it	update_page_content, save_content, save_funnel_page_content and get_page_editable_content

The page-content tools are the ones worth pausing on. They write into pages that already exist, which is a different thing from creating a funnel and its opt-in step from scratch.

What that means in practice

Funnels are the clearest case where creating is well covered and undoing is not. A funnel made through the chat window cannot be renamed or removed through it, and only opt-in steps can be created at all.

Campaign steps carry a second gap. They can be written, changed and deleted through the server, but scheduling and activating them is not supported and has to be done in the dashboard.

And a newsletter created this way always goes out under the default sender name and address in the account settings. systeme.io states those values cannot currently be changed through MCP.

The two published lists, and what they say

systeme.io publishes two accounts of this feature and they do not match each other, let alone the connection.

The developer page lists five capabilities: contacts, tags, tag assignment, contact fields and newsletters. It then states that at this stage these are the only capabilities exposed by the MCP server, and that other systeme.io features are not yet supported. It carries an "Updated 3 months ago" stamp.
The help centre, in article 9489, lists nine groups: contacts, newsletters and campaigns, funnels, price plans and coupons, automation rules, digital products, physical products, offers and sales settings, and SMS templates with booking calendar events. Six of those have a dedicated article of their own.
The live connection exposed 113 tools across the fourteen areas above.

The developer page is the one to treat with most care, because it does not merely omit things: it states that its list is complete. Courses, page editing, coupons, offers, products and automation rules are all absent from it and all present on the connection.

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.

What an absence on this page means

Every count and every tool name above was read off an MCP connection running in a live account. systeme.io publishes no list of its MCP tools, so there is no page to check them against.

So where this answer says a tool is not there, it means no tool of that name was exposed to that account on that date. That is not the same as the thing being impossible.