Bring Newsletter Management
to CrewAI
Learn how to connect Get a Newsletter to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Get a Newsletter MCP Server?
Connect your Get a Newsletter account to any AI agent and take full control of your email marketing workflows through natural conversation.
What you can do
- Subscriber Management — List, create, update, or remove email contacts directly from the cloud
- Contact Inspection — Fetch detailed metadata for specific subscribers and verify their status
- List Organization — View all active subscriber lists and create new audience segments
- Campaign Tracking — Retrieve sent and drafted email campaigns along with their details
How it works
1. Subscribe to this server
2. Enter your Get a Newsletter API Token
3. Start managing your audience from Claude, Cursor, or any MCP-compatible client
Your AI acts as a dedicated marketing assistant, ready to sync leads or pull campaign data without opening the browser.
Who is this for?
- Marketers — instantly retrieve campaign statuses or audience lists without leaving your workflow
- Engineering Teams — add or check subscribers straight from the code editor to verify integrations
- Founders — automate CRM cross-referencing by letting the agent query your active contacts
Built-in capabilities (10)
Create a new contact (subscriber)
Create a new subscriber list
Delete a contact
Get details of a specific campaign
Get details of a specific contact
Get details of a specific list
List all campaigns
List all contacts (subscribers)
List all subscriber lists
Update an existing contact
Why CrewAI?
When paired with CrewAI, Get a Newsletter becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Get a Newsletter tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Get a Newsletter in CrewAI
Get a Newsletter and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Get a Newsletter to CrewAI 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 Get a Newsletter in CrewAI
The Get a Newsletter 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 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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
Get a Newsletter for CrewAI
Every tool call from CrewAI to the Get a Newsletter MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically create a new subscriber and assign them a name?
Yes! Use the create_contact tool with the email address and optional first/last name. Your agent will instantly register them in your Get a Newsletter database.
How do I check my previous or active email campaigns?
Simply ask the agent to run the list_campaigns action. It will retrieve the latest sent, scheduled, or drafted email campaigns available in your account.
Can this integration delete my entire account or lists?
No. The integration allows targeted deletions of specific contacts (delete_contact), but it does not expose destructive actions to wipe entire lists or account-level configurations.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.