Bring Direct Mail
to CrewAI
Learn how to connect ChurchStamp 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 ChurchStamp MCP Server?
Connect your ChurchStamp account to any AI agent and take full control of your physical direct mail orchestration and automated postcard outreach through natural conversation.
What you can do
- Postal Outreach Orchestration — Programmatically send personalized postcards and letters to recipients, retrieving detailed technical status in real-time
- Campaign Intelligence — Programmatically retrieve lists of active direct mail campaigns and access complete performance metadata for your mobile outreach
- Design Portfolio Architecture — Access your complete directory of mail designs and templates to maintain a perfectly coordinated brand presence
- Delivery Monitoring — Access real-time status updates for mail pieces and track campaign progress directly through your agent for instant operational reporting
- Infrastructure Verification — Verify account-level API connectivity and monitor mailing volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your Access Token from your ChurchStamp dashboard (Settings > Security)
3. Start orchestrating your physical outreach from Claude, Cursor, or any MCP client
No more manual uploading of recipient CSVs or guessing mail delivery dates. Your AI acts as your dedicated mail coordinator and direct marketing architect.
Who is this for?
- Church Administrators — instantly trigger welcome postcards and monitor outreach campaigns using natural language commands
- Marketing Operations — verify mail design metadata and track campaign results without leaving your creative workspace
- Outreach Coordinators — automate the management of recipient lists and mail piece assignments through simple AI queries
Built-in capabilities (10)
Verify ChurchStamp API connectivity
Optionally assign a design template. Create a mail campaign
Add a contact
Get campaign details
Get design details
Get your account
List all mail campaigns
List all contacts
List all postcard designs
Send a postcard
Why CrewAI?
When paired with CrewAI, ChurchStamp becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ChurchStamp 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
ChurchStamp in CrewAI
ChurchStamp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ChurchStamp 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 ChurchStamp in CrewAI
The ChurchStamp 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
ChurchStamp for CrewAI
Every tool call from CrewAI to the ChurchStamp MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my ChurchStamp Access Token?
Log in to your account, navigate to Settings > Security, and copy your unique Access Token from the API section.
Can I send personalized postcards via AI?
Yes! The send_churchstamp_mail tool allows your agent to trigger physical mailings by providing recipient metadata and design IDs.
How do I list my mail designs?
Use the list_designs tool to retrieve your complete directory along with the unique identifiers for all managed templates.
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.