io.github.Pankaj-bit361/volaneaMCP Registry

Volanea

v1.0.2

Email infrastructure on Volanea: build templates, segments and workflows, send and check email.

Endpoint health

online

Last checked: 11/3/2026, 7:15:55 PM
Latency: 663 ms
Consecutive failures: 0

Endpoint reachable: pass
Protocol valid: pass
MCP handshake valid: pass

Machine-readable profile

mcp-server · schema v1 · callable

mcp-server:io.github.Pankaj-bit361%2Fvolanea

Profile JSON ↗

Connect this server

Generated config contains no credentials. Keep any required secrets in your client's local environment.

Client

{
  "mcpServers": {
    "io.github.Pankaj-bit361/volanea": {
      "url": "https://api.volanea.com/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

25 shown · authentication unknown

volanea_check_delivery

Inspect the send log to verify what actually happened. With `emailId`, returns that message's status, rendered HTML (truncated), engagement counters, and any error — the way to confirm a volanea_send_test_email rendered correctly. Without it, lists recent messages, optionally filtered by recipient, status, or source (transactional/campaign/workflow/inbound) — useful to confirm a workflow actually sent its email.

Schema valid · SHA-256 253d157a9c28…

View input schema

{
  "type": "object",
  "properties": {
    "emailId": {
      "type": "string",
      "description": "A specific email-… id for full detail including the rendered body."
    },
    "to": {
      "type": "string",
      "description": "Filter the list by recipient address."
    },
    "status": {
      "type": "string",
      "enum": [
        "queued",
        "sending",
        "sent",
        "delivered",
        "opened",
        "clicked",
        "bounced",
        "complained",
        "failed",
        "received"
      ],
      "description": "Filter by delivery state. Worth knowing what these mean before trusting them: `sent` means handed to the provider, NOT that it arrived — `delivered` is the confirmation. `bounced` and `complained` also create a suppression, so that recipient is blocked from future sends. In test mode nothing leaves the building, so messages stop at `sent` and never progress to `delivered`."
    },
    "source": {
      "type": "string",
      "enum": [
        "transactional",
        "campaign",
        "workflow",
        "inbound"
      ],
      "description": "Narrow the log to one origin: a direct API send, a campaign blast, a workflow step, or mail received at an inbound address. The quickest way to answer \"did my workflow actually send anything?\" without wading through unrelated traffic."
    },
    "limit": {
      "type": "number",
      "description": "Max rows when listing (default 10, max 50)."
    }
  }
}

volanea_check_recipient

Connections

streamable-http
https://api.volanea.com/mcp

Links

Website ↗Repository ↗Health JSON ↗

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

25 shown · authentication unknown

volanea_check_delivery

Schema valid · SHA-256 253d157a9c28…

View input schema

{
  "type": "object",
  "properties": {
    "emailId": {
      "type": "string",
      "description": "A specific email-… id for full detail including the rendered body."
    },
    "to": {
      "type": "string",
      "description": "Filter the list by recipient address."
    },
    "status": {
      "type": "string",
      "enum": [
        "queued",
        "sending",
        "sent",
        "delivered",
        "opened",
        "clicked",
        "bounced",
        "complained",
        "failed",
        "received"
      ],
      "description": "Filter by delivery state. Worth knowing what these mean before trusting them: `sent` means handed to the provider, NOT that it arrived — `delivered` is the confirmation. `bounced` and `complained` also create a suppression, so that recipient is blocked from future sends. In test mode nothing leaves the building, so messages stop at `sent` and never progress to `delivered`."
    },
    "source": {
      "type": "string",
      "enum": [
        "transactional",
        "campaign",
        "workflow",
        "inbound"
      ],
      "description": "Narrow the log to one origin: a direct API send, a campaign blast, a workflow step, or mail received at an inbound address. The quickest way to answer \"did my workflow actually send anything?\" without wading through unrelated traffic."
    },
    "limit": {
      "type": "number",
      "description": "Max rows when listing (default 10, max 50)."
    }
  }
}

volanea_check_recipient

{ "type": "object", "properties": { "name": { "type": "string", "description": "Internal name for the campaign list — never shown to recipients. The subject is what they see." }, "subject": { "type": "string", "description": "Subject line recipients see. Supports {{variable}} placeholders, including the {{name | \"default\"}} fallback form." }, "previewText": { "type": "string", "description": "The preview snippet most clients show beside the subject. Omit it and they fall back to the first words of the HTML, which is usually a logo alt-text or an unsubscribe line." }, "body": { "type": "string", "description": "HTML body. Supports {{variable}} placeholders." }, "fromEmail": { "type": "string", "description": "Sender address. Its domain must be verified for this project or the send is refused — check volanea_get_project_status for which domains are verified before choosing one." }, "fromName": { "type": "string", "description": "Display name shown beside the from address, e.g. \"Volanea Team\"." }, "replyTo": { "type": "string", "description": "Where replies go, if not the from address. Its domain does NOT need verifying. Point it at a real inbox — or at an inbound address, whose local part keeps its case so a ticket token survives the round trip." }, "audience": { "type": "string", "enum": [ "all", "segment", "filter" ], "description": "Who receives it. `all` = every subscribed contact. `segment` = an existing segment, and requires `segmentId`. `filter` = an inline condition tree, and requires `filter` — use it for a one-off audience you do not want to keep. Unsubscribed contacts are excluded from all three, since campaigns are marketing mail." }, "segmentId": { "type": "string", "description": "Required when audience = 'segment'." }, "filter": { "type": "object", "description": "Required when audience = 'filter'. Same condition DSL as segments.", "properties": { "logic": { "type": "string", "enum": [ "and", "or" ] }, "groups": { "type": "array", "minItems": 1, "maxItems": 20, "items": { "type": "object", "properties": { "filters": { "type": "array", "minItems": 1, "maxItems": 20, "items": { "type": "object", "properties": { "field": { "type": "string", "description": "See field namespaces in the parent description." }, "operator": { "type": "string", "description": "See valid operators in the parent description." }, "value": { "description": "Comparison value (string, number, or boolean). Omit for exists/notExists/triggered." }, "days": { "type": "number", "description": "Day window for within/olderThan/triggered/notTriggered." } }, "required": [ "field", "operator" ] } } }, "required": [ "filters" ] } } }, "required": [ "logic", "groups" ] }, "abSubjectB": { "type": "string", "description": "Variant-B subject line for an A/B test." }, "abSamplePct": { "type": "number", "description": "Percent of the audience in the A/B sample (5–50)." } }, "required": [ "name", "subject", "body", "fromEmail" ] }

{ "type": "object", "properties": { "name": { "type": "string", "description": "Segment name. Acts as the idempotency key. Not required when dryRun is true." }, "description": { "type": "string", "description": "Optional note for whoever reads the segment list later — why this audience exists, not what the filter does. The conditions already say what it does." }, "conditions": { "type": "object", "description": "Condition tree over contacts. `logic` combines the groups (\"and\"/\"or\"); filters *within* a group are always ANDed. Filter fields: `email`, `firstName`, `lastName`, `locale`, `subscribed`, `createdAt`, `data.<customField>` (discover custom fields with volanea_list_resources { resource: \"contact_fields\" }), `event.<eventName>` (product events — discover names with volanea_list_resources { resource: \"event_names\" }), and `email.opened` / `email.clicked` / `email.bounced`. Operators for plain/data fields: equals, notEquals, contains, notContains, greaterThan, lessThan, exists, notExists, within (requires `days`), olderThan (requires `days`). Operators for event.*/email.* activity fields: triggered, notTriggered (optional `days` restricts to a recent window).", "properties": { "logic": { "type": "string", "enum": [ "and", "or" ] }, "groups": { "type": "array", "minItems": 1, "maxItems": 20, "items": { "type": "object", "properties": { "filters": { "type": "array", "minItems": 1, "maxItems": 20, "items": { "type": "object", "properties": { "field": { "type": "string", "description": "See field namespaces in the parent description." }, "operator": { "type": "string", "description": "See valid operators in the parent description." }, "value": { "description": "Comparison value (string, number, or boolean). Omit for exists/notExists/triggered." }, "days": { "type": "number", "description": "Day window for within/olderThan/triggered/notTriggered." } }, "required": [ "field", "operator" ] } } }, "required": [ "filters" ] } } }, "required": [ "logic", "groups" ] }, "dryRun": { "type": "boolean", "description": "When true, only preview the match count and sample — nothing is created or modified. Two things skew a preview: any `event.<name>` or `data.<field>` this project has never recorded is reported in `warnings` (a typo matches zero contacts and looks identical to an empty audience), and contacts created by this MCP server's own tools (volanea_track_event, volanea_test_workflow) are tagged as test artifacts and are EXCLUDED from segment evaluation entirely — seeding one will not move this count." } }, "required": [ "conditions" ] }

{ "type": "object", "properties": { "name": { "type": "string", "description": "Template name, e.g. 'Welcome email'. Acts as the idempotency key." }, "type": { "type": "string", "enum": [ "transactional", "marketing" ], "description": "Decides who can receive it, so getting this wrong is a compliance problem rather than a cosmetic one. `transactional` reaches a recipient even when their contact is unsubscribed (password resets, receipts, verification codes). `marketing` is skipped for unsubscribed contacts and must carry an unsubscribe link. Default to `marketing` for anything promotional; use `transactional` only when the message is a direct response to something the user did." }, "subject": { "type": "string", "description": "Subject line. Supports {{variable}} placeholders." }, "body": { "type": "string", "description": "HTML body. Supports {{variable}} placeholders." }, "previewText": { "type": "string", "description": "Inbox preview line (~100 chars visible)." }, "fromEmail": { "type": "string", "description": "Sender address — must be on a verified domain to deliver in live mode." }, "fromName": { "type": "string", "description": "Human-readable sender name." } }, "required": [ "name", "subject", "body", "fromEmail" ] }

{ "type": "object", "properties": { "name": { "type": "string", "description": "Workflow name. Acts as the idempotency key." }, "trigger": { "type": "string", "description": "e.g. \"event:user.signed_up\" or \"contact.created\"." }, "graph": { "type": "object", "description": "Automation graph. Exactly one `trigger` node is the entry point; edges connect node ids. Node types and their `config`:\n- trigger: entry node, no config.\n- send_email: { templateId? } and/or { subject?, body? (HTML), fromEmail?, fromName? } — template fields fill anything omitted.\n- delay: { minutes?, hours?, days? } (defaults to 1 minute if all omitted).\n- wait_event: { event: \"<eventName>\", timeoutHours? (default 72) }. The unlabeled outgoing edge fires when the event arrives; an edge labeled \"timeout\" is taken on timeout.\n- condition: { conditions: <same condition tree as segments> }. Outgoing edges must be labeled \"yes\" and \"no\".\n- update_contact: { set: { <customField>: value, ... }, subscribed? }.\n- webhook: { url, payload? } — POSTs workflow/contact context to your URL (5s timeout).\n- exit: ends the walk.\n`x`/`y` are canvas coordinates for the dashboard editor — space nodes out (e.g. x = index * 260, y = 80).", "properties": { "nodes": { "type": "array", "minItems": 1, "maxItems": 100, "items": { "type": "object", "properties": { "id": { "type": "string" }, "type": { "type": "string", "enum": [ "trigger", "send_email", "delay", "wait_event", "condition", "update_contact", "webhook", "exit" ] }, "label": { "type": "string", "maxLength": 120 }, "config": { "type": "object", "additionalProperties": true }, "x": { "type": "number" }, "y": { "type": "number" } }, "required": [ "id", "type", "label", "x", "y" ] } }, "edges": { "type": "array", "maxItems": 200, "items": { "type": "object", "properties": { "from": { "type": "string" }, "to": { "type": "string" }, "label": { "type": "string", "description": "Branch label — \"yes\"/\"no\" for condition nodes, \"timeout\" for wait_event." } }, "required": [ "from", "to" ] } } }, "required": [ "nodes", "edges" ] }, "reentry": { "type": "string", "enum": [ "never", "after_exit", "always" ], "description": "Whether a contact can re-enter: never, after finishing a previous walk (default), or always." } }, "required": [ "name", "trigger", "graph" ] }

{ "type": "object", "properties": { "resource": { "type": "string", "enum": [ "Billing", "Campaigns", "Contacts", "Domains", "Emails", "Events", "Inbound", "Inboxes", "Meta", "Segments", "Send", "Stats", "Suppressions", "Templates", "Verify", "Webhooks", "Workflows" ], "description": "Which API resource to fetch reference docs for." }, "indexOnly": { "type": "boolean", "description": "Return just the operation list (operationId, method, path, summary) with no request/response schemas — the cheapest way to find the operationIds to pass in `operations`. Takes precedence over `operations`." }, "operations": { "type": "array", "items": { "type": "string" }, "description": "operationIds to expand in full, e.g. [\"sendCampaign\", \"getCampaign\"] — get them from an indexOnly call. Only the component schemas these operations actually reference are included. Omit to get every operation on the resource, which is what makes the unfiltered call so large." } }, "required": [ "resource" ] }

Endpoint health

Machine-readable profile

Connect this server

Indexed tools

volanea_check_delivery

volanea_check_recipient

Connections

Links

Endpoint health

Machine-readable profile

Connect this server

Indexed tools

volanea_check_delivery

volanea_check_recipient

Connections

Links

volanea_cleanup_test_data

volanea_create_campaign_draft

volanea_create_inbox

volanea_create_segment

volanea_create_template

volanea_create_webhook_endpoint

volanea_create_workflow

volanea_delete_resource

volanea_get_api_reference

volanea_get_project_status

volanea_get_template

volanea_get_workflow

volanea_list_resources

volanea_read_inbox

volanea_render_template

volanea_report_missing_tool

volanea_search_inbox

volanea_send_test_email

volanea_setup_domain

volanea_test_webhook_delivery

volanea_test_workflow

volanea_track_event

volanea_update_webhook_endpoint