mcp-server-systemeio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYSTEMEIO_API_KEY | Yes | Your Systeme.io API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_contactsA | List contacts in your Systeme.io account. Filter by email, tags, bounced/unsubscribed status, or registration date. Returns paginated results. |
| get_contactA | Get full details of a specific contact by their ID, including email, locale, custom fields, tags, and registration info. |
| create_contactA | Create a new contact in Systeme.io with an email address, optional locale, and custom fields. This can trigger automations (e.g., enrolling in a course or campaign). |
| update_contactA | Update an existing contact's locale or custom fields. Uses merge-patch: only specified fields are changed. |
| delete_contactB | Delete a contact from Systeme.io. Note: actual deletion may take several days for security reasons. |
| list_tagsB | List all tags in your Systeme.io account. Tags are used to segment and organize your contacts. |
| create_tagB | Create a new tag in Systeme.io. Tags help organize and segment contacts for campaigns and automations. |
| update_tagB | Rename an existing tag. |
| delete_tagA | Delete a tag from Systeme.io. This removes the tag from all contacts. |
| add_tag_to_contactA | Assign a tag to a contact. This can trigger automations in Systeme.io (e.g., adding to a campaign, enrolling in a course). |
| remove_tag_from_contactB | Remove a tag from a contact. |
| list_contact_fieldsA | List all custom contact fields defined in your Systeme.io account (e.g., first_name, country, phone_number, and any custom fields you created). |
| list_coursesB | List all online courses in your Systeme.io school. Filter by active status or search by name. |
| enroll_contact_in_courseB | Enroll a contact in an online course. You can grant full access, partial access (specific modules), or dripping content access. |
| list_enrollmentsA | List course enrollments. See which contacts are enrolled in which courses. |
| remove_enrollmentB | Remove a contact's enrollment from a course. |
| list_subscriptionsA | List payment subscriptions for a specific contact. Shows active recurring payments. |
| cancel_subscriptionA | Cancel a payment subscription. The subscription will end at the end of the current billing cycle. |
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 18 tools
Each tool targets a distinct resource-action pair (e.g., create_contact, delete_tag, enroll_contact_in_course). There is no overlap or ambiguity; all operations are clearly separated by entity and action.
All tools use consistent snake_case with a verb_noun pattern. Verbs like create, list, update, delete, add, remove are used uniformly, and prepositions are used where needed (e.g., add_tag_to_contact).
18 tools cover the core entities (contacts, tags, courses, subscriptions) with dedicated CRUD and specific actions. The count is well-scoped for the platform's domain without being excessive or insufficient.
While contacts and tags have full CRUD coverage, courses lack create, update, delete, and get operations beyond listing. This is a notable gap that could hinder course management workflows.