API Tools

volanea.com

An MCP server for Volanea that helps developers integrate its email API by exposing project status, REST API reference, resource listing, sending-domain setup, and template retrieval tools.

1 endpoint27 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://api.volanea.com/mcp

No auth detected

MCP server metadata

Name: volanea
Version: 0.1.0

Capabilities

tools

Server instructions

Volanea is an email platform (transactional sending, campaigns, automation). These tools operate the connected Volanea project while you write the integration code into the user's own codebase with your file tools. Suggested flow: volanea_get_project_status → volanea_get_api_reference for the resources you will call → create templates/segments/workflows → write the sending and webhook code into their app → verify with volanea_send_test_email + volanea_check_delivery and volanea_track_event + volanea_test_workflow. Always verify your work before reporting success: a rendered test email read back from the log, or a workflow run log showing the steps executed. Test sends never reach real inboxes. Campaigns are created as drafts only — a human sends them. This connection is unauthenticated: the tool list is readable, but every tool requires a credential. Pass `Authorization: Bearer sk_…` (a project key), or complete the OAuth flow this server advertises — a tools/call without a token answers 401 with the resource_metadata challenge that starts it.

Known tools 27

volanea_get_project_status

Call this FIRST in any integration session.

Inferred read-only

volanea_get_api_reference

Authoritative REST API reference for writing integration code into the user's app.

Inferred read-only

volanea_list_resources

List existing resources of one kind — use to find ids and avoid duplicating work.

Inferred read-only

volanea_setup_domain

Add a sending domain and/or check its DNS.

Inferred read-only

volanea_get_template

Read ONE template in full — subject, HTML body, fromEmail, type, version, and the {{variables}} it expects.

Inferred read-only

volanea_render_template

Render a template with sample variables and return the resulting subject and HTML, plus any {{placeholders}} that went unsubstituted — WITHOUT sending anything or writing a row to the send log.

Potential side effects

volanea_create_template

Create a reusable email template with {{variable}} placeholders.

Potential side effects

volanea_create_segment

Create a dynamic audience segment from a condition tree (membership recomputes automatically).

Potential side effects

volanea_get_workflow

Read ONE workflow in full — the complete node/edge graph with every node's config and canvas position, plus per-node run counts.

Inferred read-only

volanea_create_workflow

Create an event-triggered automation workflow from a node/edge graph.

Potential side effects

volanea_update_workflow

Update a workflow by id — edit the graph/trigger, or set status to 'active' (start processing live events) or 'paused'.

Potential side effects

volanea_test_workflow

END-TO-END TEST for an automation.

Inferred read-only

volanea_track_event

Send a product event exactly as the user's app would (POST /v1/events).

Potential side effects

volanea_check_recipient

Answer "can I actually send to this address?

Potential side effects

volanea_send_test_email

Render and send a test message — either a saved template (`templateId` + sample `variables`) or ad-hoc `subject`/`html`.

Potential side effects

volanea_check_delivery

Inspect the send log to verify what actually happened.

Potential side effects

volanea_create_webhook_endpoint

Register an endpoint in the user's app to receive Volanea events, and get back its `whsec_…` SIGNING SECRET — you need that secret to write the signature-verification code into their codebase (see volanea_get_api_reference { resource: 'Webhooks' } for the X-Volanea-Signature scheme).

Potential side effects

volanea_test_webhook_delivery

Send a REAL signed test delivery to a registered endpoint and return what the endpoint answered — status code, response body, and the exact X-Volanea-Signature header sent.

Potential side effects

volanea_create_campaign_draft

Create a campaign as a DRAFT for the user to review and send from the dashboard.

Potential side effects

volanea_create_inbox

Create an email inbox an agent can receive mail at (private beta — answers `inboxes_not_enabled` if the project isn't in it).

Potential side effects

volanea_read_inbox

Read an inbox.

Inferred read-only

volanea_wait_for_email

Wait (up to 55 s) for an email to arrive in an inbox and return it in full — the way to pick up a verification code, magic link, or reply.

Potential side effects

volanea_search_inbox

Full-text search one inbox's mail — subject, sender, and reply text — best match first.

Inferred read-only

volanea_cleanup_test_data

Remove the test artifacts YOU created in this project — the templates, segments, workflows, webhook endpoints, and campaign drafts made through this MCP server, plus any contacts it auto-created while enrolling or tracking.

Potential side effects

volanea_update_webhook_endpoint

Change an existing webhook endpoint — flip `enabled`, repoint `url` after a tunnel restarts, or change which events it subscribes to.

Inferred read-only

volanea_delete_resource

Permanently delete ONE resource by id.

Potential side effects

volanea_report_missing_tool

Report that this server lacks a tool you needed, so the gap gets closed instead of silently worked around.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.volanea]
url = "https://api.volanea.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "volanea": {
      "type": "http",
      "url": "https://api.volanea.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: volanea
Remote MCP URL: https://api.volanea.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "volanea": {
      "url": "https://api.volanea.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "volanea": {
      "type": "http",
      "url": "https://api.volanea.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "volanea",
  "transport": "streamable-http",
  "url": "https://api.volanea.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.