Bring Sms Marketing
to CrewAI
Learn how to connect Postscript to CrewAI 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 Postscript MCP Server?
Connect your Postscript account to any AI agent and take full control of your SMS marketing orchestration through natural conversation. Postscript is the leading SMS platform for Shopify stores, and this integration allows you to retrieve subscriber metadata, monitor campaign performance, and manage automated keywords directly from your chat interface.
What you can do
- Subscriber & Audience Orchestration — List all managed SMS subscribers and retrieve detailed profile metadata programmatically to ensure your outreach is always synchronized.
- Campaign & Flow Intelligence — Access and monitor your SMS campaigns and automated flows (like abandoned cart recovery) directly from the AI interface to track engagement metrics.
- Keyword & Opt-in Control — List and search through your mobile keywords to maintain a clear overview of your subscription sources via natural language.
- Operational Monitoring — Track system responses and manage webhook metadata using simple AI commands.
- Account Visibility — Access high-level account and plan metadata to ensure your SMS operations are always optimized.
How it works
1. Subscribe to this server
2. Enter your Postscript Private API Key from your account settings
3. Start managing your SMS automation from Claude, Cursor, or any MCP-compatible client
No more manual dashboard checking for subscriber status. Your AI acts as a dedicated SMS marketing coordinator or growth manager.
Who is this for?
- Shopify Store Owners — quickly retrieve subscriber summaries and monitor campaign reach without switching apps.
- E-commerce Marketers — automate the discovery of top-performing keywords and track automated flows via natural conversation.
- Operations Teams — streamline the retrieval of SMS metadata and monitor organizational growth health directly within the chat.
Built-in capabilities (12)
Note: Compliance rules apply. Subscribe a new user
Create a new webhook
Delete a webhook
Get account details
Get campaign details
Get subscriber details
g., Abandoned Cart). List SMS automations
List SMS campaigns
List SMS keywords
List all SMS subscribers
List active webhooks
Update subscriber info
Why CrewAI?
When paired with CrewAI, Postscript becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Postscript 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
Postscript in CrewAI
Postscript and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Postscript 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 Postscript in CrewAI
The Postscript 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 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
Postscript for CrewAI
Every tool call from CrewAI to the Postscript 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 find the details for a specific SMS subscriber by providing their ID?
Yes! Use the get_subscriber tool with the Subscriber ID. Your agent will respond with the complete metadata for the profile, including opt-in status and association keywords in seconds.
How do I find my Postscript Private API Key?
Log in to your Postscript account, navigate to Settings > API, and you will find your unique secret Private Key (starting with sk-) there.
Can I use the AI to see my SMS campaigns?
Absolutely. Use the list_campaigns tool to retrieve all your sent and scheduled SMS campaigns, along with their metadata and performance metrics.
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.