Systeme.io MCP server for sales and pages
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Systeme.io through Cotlet.dev. Call systeme_io_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| systeme_io_guideA | How to work in Systeme.io (funnels, email campaigns, sales and blog publishing): its screens and the sign-in link. Call this first. |
| systeme_io_statusA | Check that your Cotlet.dev account and Systeme.io are ready: account, credits and Systeme.io connection. |
| systeme_io_openA | Open a Systeme.io page in your signed-in Cloud Browser (default https://systeme.io) to work with funnels, email campaigns, sales and blog publishing. |
| systeme_io_readA | Read the current Systeme.io page: its text and numbered buttons, links and fields. |
| systeme_io_clickB | Click a numbered element on the current Systeme.io page. |
| systeme_io_typeC | Type text into a numbered field on the current Systeme.io page. |
| systeme_io_closeA | Close the Systeme.io browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct browser-automation primitive (open, read, click, type, close) or a distinct meta function (guide, status), so misselection is unlikely. The only soft overlap is guide vs. status, both framed as things to do first, but their descriptions clarify the difference.
Every tool uses the same systeme_io_ prefix followed by a single clear verb (guide, status, open, read, click, type, close). The pattern is uniform snake_case with no deviations.
Seven tools is well-scoped for a browser-driven integration: one session lifecycle pair, three page-interaction primitives, and two onboarding helpers. Nothing feels redundant or padded.
The core interaction loop (open, read, click, type, close) is covered, but there are notable gaps for the stated domain: no navigation to a specific URL, no select/dropdown handling for funnel and campaign forms, and no keypress/scroll/wait primitives. Agents can partially work around these via click and type, but form-building workflows will hit dead ends.