emailoctopus
Server Details
Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
13 toolsemailoctopus_create_contactCreate contactDestructiveInspect
CREATES a new contact in a list — this MODIFIES live data (adds a subscriber). email_address is required; optionally set fields (keyed by field tag), tags, and status. EmailOctopus: POST /lists/{list_id}/contacts. Returns the created contact.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags to apply to the contact, e.g. ["vip", "beta"]. | |
| fields | No | Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}). | |
| status | No | Subscription status: subscribed, pending, or unsubscribed. | |
| list_id | Yes | The list's id to add the contact to. | |
| email_address | Yes | The contact's email address. |
emailoctopus_create_listCreate listDestructiveInspect
CREATES a new list — this MODIFIES live data. Provide a name. EmailOctopus: POST /lists. Returns the created list.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Human-readable name for the new list. |
emailoctopus_delete_contactDelete contactDestructiveInspect
PERMANENTLY REMOVES a contact from a list — this MODIFIES live data and cannot be undone. contact_id is the MD5 hash of the lowercased email address, or the id from list_contacts. EmailOctopus: DELETE /lists/{list_id}/contacts/{contact_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| list_id | Yes | The list's id. | |
| contact_id | Yes | The contact's id to delete — the MD5 hash of the lowercased email address, or the id from list_contacts. |
emailoctopus_get_campaignGet campaignRead-onlyInspect
Get a single campaign by its id. Returns the campaign's full state — name, status, subject, from, content, and created_at. EmailOctopus: GET /campaigns/{campaign_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | The campaign's id. |
emailoctopus_get_campaign_links_reportGet campaign links reportRead-onlyInspect
Get a campaign's per-link click report — for each link in the campaign, the URL and its click counts. EmailOctopus: GET /campaigns/{campaign_id}/reports/links.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | The campaign's id. |
emailoctopus_get_campaign_reportGet campaign reportRead-onlyInspect
Get a campaign's aggregate performance report — sent, opened, clicked, bounced, unsubscribed, complained, and related counts. EmailOctopus: GET /campaigns/{campaign_id}/reports/summary.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | The campaign's id. |
emailoctopus_get_contactGet contactRead-onlyInspect
Get a single contact in a list. Returns email_address, fields, tags, status, and created_at. contact_id is the MD5 hash of the lowercased email address, or the id returned by emailoctopus_list_contacts. EmailOctopus: GET /lists/{list_id}/contacts/{contact_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| list_id | Yes | The list's id. | |
| contact_id | Yes | The contact's id — the MD5 hash of the lowercased email address, or the id from list_contacts. |
emailoctopus_get_listGet listRead-onlyInspect
Get a single list by its id. Returns the list's full state — name, contact counts by status, and created_at. EmailOctopus: GET /lists/{list_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| list_id | Yes | The list's id. |
emailoctopus_list_campaignsList campaignsRead-onlyInspect
List all campaigns in the account. Returns {data:[...],paging:{...}} — each campaign's id, name, status, subject, and created_at. Paginate with limit (max 100) and starting_after. EmailOctopus: GET /campaigns.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max campaigns to return (1..100). | |
| starting_after | No | Pagination cursor — the id to start after (from the previous page's paging). |
emailoctopus_list_contactsList contactsRead-onlyInspect
List the contacts in a list. Returns {data:[...],paging:{...}} — each contact's id, email_address, fields, tags, status, and created_at. Paginate with limit (max 100) and starting_after. EmailOctopus: GET /lists/{list_id}/contacts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max contacts to return (1..100). | |
| list_id | Yes | The list's id. | |
| starting_after | No | Pagination cursor — the id to start after (from the previous page's paging). |
emailoctopus_list_listsList listsRead-onlyInspect
List all lists in the account. Returns {data:[...],paging:{...}} — each list's id, name, contact counts by status, and created_at. Paginate with limit (max 100) and starting_after (cursor from the previous page). EmailOctopus: GET /lists.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max lists to return (1..100). | |
| starting_after | No | Pagination cursor — the id to start after (from the previous page's paging). |
emailoctopus_update_contactUpdate contactDestructiveInspect
UPDATES an existing contact in a list — this MODIFIES live data. Send only the fields you want to change (email_address, fields, tags, status). contact_id is the MD5 hash of the lowercased email address, or the id from list_contacts. EmailOctopus: PUT /lists/{list_id}/contacts/{contact_id}. Returns the updated contact.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags to apply to the contact, e.g. ["vip", "beta"]. | |
| fields | No | Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}). | |
| status | No | Subscription status: subscribed, pending, or unsubscribed. | |
| list_id | Yes | The list's id. | |
| contact_id | Yes | The contact's id — the MD5 hash of the lowercased email address, or the id from list_contacts. | |
| email_address | No | The contact's email address. |
emailoctopus_update_listUpdate listDestructiveInspect
UPDATES an existing list by id — this MODIFIES live data. Sets the list's name. EmailOctopus: PUT /lists/{list_id}. Returns the updated list.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The new name for the list. | |
| list_id | Yes | The list's id to update. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!