Server Details
Generate hyper-personalized cold email sequences via MachFive API.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Bluecraft-AI/machfive-mcp
- GitHub Stars
- 2
- Server Listing
- MachFive Cold Email
See and control every tool call
Available Tools
6 toolsexport_listInspect
Download 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. |
generate_batchInspect
Submit 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. |
generate_sequenceInspect
Generate 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. |
get_list_statusInspect
Check 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. |
list_campaignsInspect
List 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. |
list_listsInspect
List 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. |
Verify Ownership
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 verified, the connector will appear as claimed by you.
Last verification attempt failed.
Hostname/IP does not match certificate's altnames: Host: mcp.machfive.io. is not in the cert's altnames: DNS:*.up.railway.app
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!
Your Connectors
Sign in to create a connector for this server.