Why CLI-First?
SendyKit chose CLI over MCP for agent integration. Here’s why:| Factor | CLI | MCP Server |
|---|---|---|
| Setup | Zero — agents already have bash | Install server, configure transport |
| Debugging | Visible request/response | Opaque protocol layer |
| Composability | Pipes, loops, jq, grep | Single tool calls |
| Compatibility | Every agent with shell access | Only MCP-compatible agents |
| Maintenance | None — CLI is the product | Separate codebase to maintain |
Example Agent Workflows
”Add this lead to the onboarding drip"
"Show me the best performing campaign this month"
"Create a re-engagement campaign for inactive subscribers"
"Run a full health check and fix what you can"
"What’s my deliverability looking like?”
Skill File
For structured agent integration, add aSKILL.md to your agent’s skills directory:
Machine Payments
For agents without shell access, SendyKit’s machine-paid path is Stripe-native machine payments. UseX-Stripe-Machine-Payment proofs for premium actions.