Bring Cold Outreach
to Cline
Learn how to connect Mailshake to Cline and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Mailshake MCP Server?
Connect your Mailshake account to any AI agent and manage sales outreach through natural conversation.
What you can do
- Campaign Management — Create and manage outreach campaigns
- Lead Tracking — Browse leads with engagement status and activity
- Sequence Management — Configure multi-step email sequences
- Reply Monitoring — Track replies, opens, and click activity
- Team Performance — Monitor team outreach metrics and quotas
- Lead Lists — Import and manage prospect lists
How it works
1. Subscribe to this server
2. Enter your Mailshake API Key
3. Start managing outreach from Claude, Cursor, or any MCP-compatible client
Who is this for?
- SDRs — manage outbound campaigns and track engagement
- Sales Teams — monitor reply rates and lead quality
- Growth — scale cold outreach with analytics
Built-in capabilities (12)
Add new prospects
Get campaign info
Get account team
Get profile info
List recipients
List cold email campaigns
Get open/click activity
List qualified leads
Stop campaign sending
Stop outreach for user
Resume campaign sending
g., Reply, Won, Lost, Ignored). Set lead stage
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Mailshake tool calls without waiting for prompts between steps. Connect 12 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
Mailshake in Cline
Mailshake and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mailshake 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Mailshake in Cline
The Mailshake 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 12 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.

* 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
How Vinkius secures
Mailshake for Cline
Every tool call from Cline to the Mailshake MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I manage outreach campaigns and sequences?
Yes. Create campaigns with multi-step sequences, personalize emails, and track engagement through each step.
How does Mailshake authentication work?
Mailshake uses HTTP Basic Auth with the API Key against api.mailshake.com/2017-04-01.
Can I track replies and lead engagement?
Yes. Monitor replies, categorize as interested/not interested, and track opens and clicks per lead.
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.
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.
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.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.
