Generate hyper-personalized cold email sequences via MachFive API.
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.
Average 4.5/5 across 6 of 6 tools scored.
Each tool has a clearly distinct purpose with no overlap: export_list retrieves completed results, generate_batch initiates batch processing, generate_sequence handles single leads synchronously, get_list_status checks status, list_campaigns lists campaigns, and list_lists lists batch jobs. The descriptions explicitly differentiate their roles, preventing misselection.
All tool names follow a consistent verb_noun pattern (e.g., export_list, generate_batch, list_campaigns) with clear, descriptive terms. There are no deviations in style or convention, making the set predictable and easy to understand.
With 6 tools, this server is well-scoped for email sequence generation and management. Each tool serves a specific function in the workflow, from setup (list_campaigns) to execution (generate_sequence/generate_batch) and retrieval (export_list/get_list_status), with no unnecessary redundancy.
The tool set covers the core lifecycle of email sequence generation: listing campaigns, generating sequences (both single and batch), checking status, and exporting results. A minor gap is the lack of tools for managing campaigns (e.g., create/update/delete campaigns), but agents can still perform essential workflows effectively.
export_listExport ListDownload the generated email sequences for a COMPLETED list.
Only call this AFTER get_list_status shows processing_status = 'completed'. If the list is not yet completed, you'll get a 409 error — poll first.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format: 'json' (structured data) or 'csv' (raw CSV for sending tools). | json |
| list_id | Yes | List UUID to export. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
generate_batchGenerate BatchInspectSubmit multiple leads for batch email sequence generation (ASYNC).
Returns IMMEDIATELY with a list_id. Processing runs in the background. After calling this, poll get_list_status every 15-30 seconds until processing_status is 'completed' or 'failed', then call export_list.
You must have a campaign_id first. Call list_campaigns if you don't have one.
| Name | Required | Description | Default |
|---|---|---|---|
| list_name | No | Display name for this batch in MachFive UI. | |
| leads_json | Yes | JSON array of lead objects. Each MUST have "email". Optional: name, title, company, company_website, linkedin_url. Example: '[{"email":"jane@acme.com","name":"Jane Doe"}]' | |
| campaign_id | Yes | Campaign UUID from list_campaigns. | |
| email_count | No | Number of emails per lead, 1-5. | |
| approved_ctas | No | Comma-separated CTAs. Omit to use campaign defaults. | |
| campaign_angle | No | Additional context/angle for personalization. | |
| email_signature | No | Signature appended to each email. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
generate_sequenceGenerate Email SequenceInspectGenerate a personalized cold email sequence for ONE lead.
This is SYNCHRONOUS — the request takes 3-10 minutes because MachFive researches the prospect and crafts unique emails. Do NOT retry if it seems slow; wait for the response.
You must have a campaign_id first. Call list_campaigns if you don't have one. If the request times out, use the returned list_id with get_list_status and export_list to recover results.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Lead's full name (improves personalization). | |
| Yes | Lead's email address (REQUIRED). | ||
| title | No | Lead's job title (improves personalization). | |
| company | No | Lead's company name (improves personalization). | |
| list_name | No | Display name for this list in MachFive UI. | |
| campaign_id | Yes | Campaign UUID from list_campaigns. | |
| email_count | No | Number of emails in sequence, 1-5. | |
| linkedin_url | No | LinkedIn profile URL for deeper personalization. | |
| approved_ctas | No | Comma-separated CTAs, e.g. 'Direct Meeting CTA, Lead Magnet CTA'. Omit to use campaign defaults. | |
| campaign_angle | No | Additional context/angle for personalization. | |
| company_website | No | Company URL for AI research. | |
| email_signature | No | Signature appended to each email. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_list_statusGet List StatusCheck the processing status of a lead list.
Use this to POLL after calling generate_batch. Call every 15-30 seconds until processing_status is 'completed' or 'failed'. When completed, call export_list. When failed, submit a new batch.
| Name | Required | Description | Default |
|---|---|---|---|
| list_id | Yes | List UUID from generate_batch or generate_sequence response. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_campaignsList CampaignsList campaigns in the user's MachFive workspace.
CALL THIS FIRST before generate_sequence or generate_batch — you need a campaign ID to generate emails. If the user hasn't specified a campaign, call this and ask them to pick one.
Returns JSON array of campaigns with id, name, and created_at. Use the 'id' field as campaign_id in generate calls.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search string to filter campaigns by name (case-insensitive substring match). Leave empty to list all. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_listsList Lead ListsList lead lists (batch jobs) in the user's MachFive workspace.
Useful for browsing past batches, checking what's in progress, or finding a list_id to export. Results are ordered newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results to return, 1-100. | |
| offset | No | Pagination offset. | |
| status | No | Filter by processing status: 'pending', 'processing', 'completed', or 'failed'. | |
| campaign_id | No | Filter by campaign UUID. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
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.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.