3,400+ MCP servers ready to use
Vinkius

Bring Subscriber Management
to Cline

Learn how to connect Smaily to Cline and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Create SubscriberDelete SubscriberGet AutomationGet CampaignGet Subscriber DetailsGet TemplateList AutomationsList Email CampaignsList Email TemplatesList SubscribersSend Automation Email

What is the Smaily MCP Server?

Connect your Smaily account to any AI agent and simplify your email marketing and automation workflows through natural conversation.

What you can do

  • Subscriber Management — List all contacts in your database, retrieve detailed profile metadata, and create new subscribers programmatically
  • Campaign Control — Query past and scheduled email campaigns to monitor your marketing outreach
  • Automation & Autoresponders — List configured automated workflows and trigger specific autoresponder emails directly from your agent
  • Template catalog — Query available email templates to choose the right look for your messages
  • Operational tracking — Stay on top of your marketing performance and subscriber engagement

How it works

1. Subscribe to this server
2. Enter your Smaily Subdomain, API User, and API Password from your account settings
3. Start managing your email marketing from Claude, Cursor, or any MCP-compatible client

Built-in capabilities (11)

create_subscriber

Add a new subscriber

delete_subscriber

Remove a subscriber

get_automation

Get details for an automation workflow

get_campaign

Get details for a specific campaign

get_subscriber_details

Get details for a specific subscriber

get_template

Get details for an email template

list_automations

List automated responders

list_email_campaigns

List email campaigns

list_email_templates

List message templates

list_subscribers

List Smaily subscribers

send_automation_email

Trigger an automation email

Why Cline?

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Smaily tool calls without waiting for prompts between steps. Connect 11 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

  • Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

  • Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

  • Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

  • Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

See it in action

Smaily in Cline

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Smaily and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Smaily to Cline through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Smaily in Cline

The Smaily MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cline only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Smaily
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Smaily for Cline

Every tool call from Cline to the Smaily MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I list all my email templates using my AI agent?

Yes! Use the list_email_templates tool to retrieve a comprehensive list of all message templates available in your Smaily account.

02

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.

03

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.

04

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

05

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.