Bring Direct Mail
to LangChain
Learn how to connect ChurchStamp to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with ChurchStamp through native MCP adapters. Connect 10 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine ChurchStamp MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across ChurchStamp queries for multi-turn workflows
ChurchStamp in LangChain
ChurchStamp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ChurchStamp to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters