$ ~/registry/skill/composiohq-composio-skills-mailersend-automation

SKILL

mailersend-automation

Name: mailersend-automation
Author: Composio

Automate MailerSend sending and management tasks through Rube MCP workflows.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This is not a purely local prompt artifact; it directs users to use Rube MCP/Composio to connect to remote services and perform Mailersend operations. No clear malicious or over-privileged red flags are evident, but its network egress, remote tool execution, and third-party connection model warrant caution. The high-star open-source source materially lowers the supply-chain risk.

CredentialsCaution

The material claims 'no API keys needed,' but it also requires creating an active `mailersend` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth-link flow, which implies third-party account authorization or token handling in practice. It does not explicitly ask for local secret exposure, but credentials are still managed through the Rube/Composio connection model, creating normal credential-use risk.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing actions through the Composio/Mailersend toolchain. User inputs, tool queries, session IDs, and execution arguments may be sent to Rube/Composio and related services. The egress targets appear aligned with the stated function, with no unrelated or hidden endpoints disclosed, so this is caution rather than high risk.

Code executionCaution

The README points to remote tool execution capabilities such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, which are external automation calls via MCP rather than arbitrary local code execution. The material does not state any need for elevated local privileges, shell injection, or system-level control, but remote execution through third-party tools still warrants normal caution.

Data accessCaution

This skill is designed for Mailersend automation and, by description, can access remote account data and operations related to email sending/management. The documentation also requires session reuse, pagination handling, and a memory parameter, indicating the toolchain may process some business data and workflow context. There is no stated ability to directly read/write local files or request obviously excessive system data permissions.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (64.7k stars), which is a significant positive signal for auditability and trust. The skill material shown here is closer to documentation/prompting guidance; although the license is unspecified and maintenance status is unknown, there are no signs of closed-source distribution, opaque installers, or obvious supply-chain red flags.

Recommendations

Only establish the connection after confirming trust in the Rube/Composio and Mailersend authorization chain, and review the granted scopes.
Avoid sending unnecessary sensitive email content, contact data, or business secrets in queries, memory, or tool arguments.
Use a least-privilege Mailersend account/workspace for testing and regularly review or revoke connections that are no longer needed.
Before production use, verify `rube.app`, the Composio documentation, and the relevant tool schemas to confirm expected egress paths and functional scope.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "mailersend-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/mailersend-automation/SKILL.md
2. Save it as ~/.claude/skills/mailersend-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Mailersend Automation via Rube MCP

Automate Mailersend operations through Composio's Mailersend toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/mailersend

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Mailersend connection via RUBE_MANAGE_CONNECTIONS with toolkit mailersend
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit mailersend
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Mailersend operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Mailersend task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mailersend"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Mailersend-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mailersend`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Mailbluster marketing tasks via Rube MCP using current tool schemas.

ComposioGet→

$ loading_