EmailOctopus MCP Server for CursorGive Cursor instant access to 12 tools to Add Contact To List, Create Email List, Get Campaign Details, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The EmailOctopus app connector for Cursor is a standout in the Productivity category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install EmailOctopus and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"emailoctopus-alternative": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About EmailOctopus MCP Server
Connect your EmailOctopus (v2) account to any AI agent and take full control of your email marketing and subscriber engagement workflows through natural conversation.
Cursor's Agent mode turns EmailOctopus into an in-editor superpower. Ask Cursor to generate code using live data from EmailOctopus and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Audience Orchestration — List and manage your email marketing lists programmatically, including creating new lists and monitoring subscriber counts
- Subscriber Lifecycle — Programmatically add, update, or remove subscribers from lists and manage detailed profiles, tags, and custom fields
- Campaign Management — Monitor sent and draft campaigns and retrieve high-fidelity performance reports including open and click rates
- Workflow Automation — Programmatically trigger automated sequences (workflows) for specific contacts to coordinate complex customer journeys
- Operational Visibility — Retrieve complete list metadata and individual contact details directly through your agent for instant marketing reporting
The EmailOctopus MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 EmailOctopus tools available for Cursor
When Cursor connects to EmailOctopus through Vinkius, your AI agent gets direct access to every tool listed below — spanning emailoctopus, email-marketing, automation-api, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Add a new contact to a list
Create a new subscriber list
Get details for a campaign
Get performance metrics for a campaign
Get details for a contact
Get details for an email list
Can filter by status. List contacts in a specific list
List all sent and draft campaigns
List all subscriber lists
Delete a contact from a list
Requires API trigger to be enabled. Start an automation for a contact
Update an existing contact
Connect EmailOctopus to Cursor via MCP
Follow these steps to wire EmailOctopus into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using EmailOctopus
Why Use Cursor with the EmailOctopus MCP Server
Cursor AI Code Editor provides unique advantages when paired with EmailOctopus through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
EmailOctopus + Cursor Use Cases
Practical scenarios where Cursor combined with the EmailOctopus MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for EmailOctopus in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with EmailOctopus immediately.
"List all my email subscriber lists in EmailOctopus."
"Add subscriber 'john.doe@example.com' to list 'l_123' with tag 'Customer'."
"Show me the report summary for campaign ID 'c_987'."
Troubleshooting EmailOctopus MCP Server with Cursor
Common issues when connecting EmailOctopus to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
EmailOctopus + Cursor FAQ
Common questions about integrating EmailOctopus MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.