Meser10 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MESER10_MODE | No | Safety mode. The server starts read-only. Allowed values: read (default; the Get* family, 16 tools), write (adds contacts, groups, campaign drafts; +27 tools), send (delivers to real recipients, spends credit; +13 tools), destructive (permanent deletes; +5 tools). | read |
| MESER10_API_KEY | Yes | Issued in the Meser10 UI. Required for authentication. | |
| MESER10_USER_ID | No | Your Meser10 account number. Optional at start-up: 17 of the 61 operations are authenticated by the key alone, while the other 44 require an explicit account number. Set it unless you know you only need the first group. The account number is an identifier, not a secret. | |
| MESER10_EXPOSE_LEGACY | No | When true, exposes the legacy Ex/Ex2 operation families that are otherwise hidden. Default false. | false |
| MESER10_MAX_RECIPIENTS | No | Refuses any single send that targets more addresses than the cap. Default 100. | 100 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_groupsA | List the mailing lists on the account, with their ids. Start here - most other calls take a group. Read-only. SOAP operation: GetGroupsList. |
| get_campaign_summaryB | Totals for one campaign: sent, opened, clicked, bounced. Read-only. SOAP operation: GetCampaignResultSummary. |
| get_campaign_detailsC | Per-recipient outcome for one campaign. Read-only. SOAP operation: GetCampaignResultDetails. |
| get_campaign_results_by_dateD | Calls GetCampaignResultsBetweenDates on the Meser10 platform. Read-only. SOAP operation: GetCampaignResultsBetweenDates. |
| get_transactional_results_by_dateD | Calls GetSingleMessagesResultsBetweenDatesEx on the Meser10 platform. Read-only. SOAP operation: GetSingleMessagesResultsBetweenDatesEx. |
| get_transactional_results_by_idC | Calls GetSingleMessagesResultsByIds on the Meser10 platform. Read-only. SOAP operation: GetSingleMessagesResultsByIds. |
| get_groupsC | Calls GetGroups on the Meser10 platform. Read-only. SOAP operation: GetGroups. |
| list_campaignsC | Calls GetCampaignsBasicInfo on the Meser10 platform. Read-only. SOAP operation: GetCampaignsBasicInfo. |
| get_campaignC | Calls GetCampaign on the Meser10 platform. Read-only. SOAP operation: GetCampaign. |
| get_campaign_link_clicksD | Calls GetCampaignLinkClicks on the Meser10 platform. Read-only. SOAP operation: GetCampaignLinkClicks. |
| get_campaign_link_clicks_by_dateD | Calls GetCampaignLinkClicksBetweenDates on the Meser10 platform. Read-only. SOAP operation: GetCampaignLinkClicksBetweenDates. |
| get_coupon_statusD | Calls GetCouponStatus on the Meser10 platform. Read-only. SOAP operation: GetCouponStatus. |
| list_unsubscribed_addressesB | Addresses that asked to be removed. Never re-add these. Read-only. SOAP operation: GetRemovedEMailAddresses. |
| list_bounced_addressesB | Addresses that hard-bounced. Feed these back into your own suppression list. Read-only. SOAP operation: GetBouncedAddresses. |
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 14 tools
Most tools have distinct scopes by campaign, date range, link clicks, transactional results, or suppression lists. However list_groups and get_groups appear to overlap heavily, both returning groups/lists, which creates a real selection ambiguity. The many campaign-result variants are mostly differentiated by descriptions.
Names are consistently snake_case and use recognizable get_/list_ verb prefixes for read-only operations. The main inconsistency is list_groups versus get_groups, where one resource is named with two different verb conventions.
14 tools is a reasonable size for a reporting-focused email marketing integration. The count is slightly inflated by near-duplicates like list_groups/get_groups and several campaign-result variants that could potentially be consolidated.
The surface covers campaign reporting, transactional results, link clicks, groups, coupon status, and suppression lists. But it is entirely read-only, so sending, creating, updating, and suppression-list management are absent if the server is meant as a full platform integration.