Flodesk MCP Server
Related Servers
Alternatives to Flodesk MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables AI agents to author and manage workflows, agents, tools, skills, policies, and reference docs in an Axonity tenant via the public REST API, with guardrails preventing direct publishing and secret exposure.10039 npmMIT- FlicenseBqualityBmaintenanceEnables AI clients to discover current fal.ai model schemas and pricing, submit only approved generation batches, manage assets, collections, tags, characters, and CDN access settings, and use isolated private account profiles through shared validated tools.66-

Arsel MCP Serverofficial
AlicenseBqualityCmaintenanceEnables AI agents to read and manage contacts, lists, tags, events, templates, campaigns and message logs in an Arsel organization, and to draft email, SMS, push and in-app campaigns for review. It is read-and-draft only, so agents can create and update records but cannot send, schedule or delete anything.59MIT- FlicenseCqualityBmaintenanceIt enables AI agents and command-line users to manage short links, analytics, conversions, partner workflows, commissions, payouts, and private workspace profiles with explicit write controls and exact reviewed batch submissions.61-

@sendraven/mcpofficial
AlicenseBqualityBmaintenanceEnables AI agents to send and manage email, read threaded replies, run campaigns and automations, and handle approvals through the Model Context Protocol from any compatible client.451,022 npm1MIT- AlicenseAqualityAmaintenanceEnables MCP clients to read Instantly.ai analytics and manage leads, campaigns, Unibox, sender accounts, blocklist, and webhooks, with write actions gated behind confirm prompts and configurable safety policies.4099 PyPIMIT
TDQS
Scored across 32 tools
Most tools target distinct resources, but list_custom_fields and list_all_custom_fields are near-duplicates, and the batch surface (batch_create_or_update_subscribers, preview_subscriber_batch, submit_subscriber_batch) plus get_subscriber vs save_subscriber_page create real selection ambiguity.
Names predominantly follow a snake_case verb_noun convention (list_webhooks, create_segment, add_subscriber_to_workflow), which is highly predictable, with only minor deviations like the bare 'unsubscribe'.
32 tools is heavy for the domain and includes several auxiliary/local utilities (get_operation_schema, list_accounts, get_oauth_userinfo, save_subscriber_page) that inflate the surface beyond core marketing operations.
Webhooks have full CRUD and subscribers are well covered, but segments and custom fields lack update/delete, and campaigns only support list/publish with no get or update, leaving notable lifecycle gaps.