How to Use the ChurchStamp MCP in LangChain

Q: How do I handle failed postcard runs in ChurchStamp with LangChain?

Use LangSmith to trace the exact tool call payload when sendmail executes. You can wrap the tool call in a standard try-catch block within your chain to handle API timeouts gracefully.

Q: Can my LangChain agent select designs from ChurchStamp automatically?

Yes, your agent can call listdesigns to retrieve available templates, then use a LLM decision step to select the best match. The chosen design ID is then passed straight to createcampaign in the next link of the chain.

Q: How do I manage multi-server MCP setups with ChurchStamp and LangChain?

You initialize MultiServerMCPClient containing the ChurchStamp endpoint alongside your other servers. LangChain aggregates these tools, allowing your agent to pull member data from a database and immediately pass it to createcontact.

Q: How do I check my remaining mailing budget before sending?

Call getuserdetails at the start of your run to inspect your account balance. Your agent can read this balance and halt the pipeline if you lack funds for the current postcard batch.

Q: How does this MCP Server secure our congregation's physical addresses?

All contact data processed by createcontact runs inside an isolated Vinkius V8 sandbox that destroys itself immediately after the tool execution finishes. No member addresses or postcard designs are stored on Vinkius servers, ensuring your church's directory remains strictly private.

Build LangChain pipelines that automatically design and ship physical postcards to your congregation members.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ChurchStamp MCP to LangChain

Create your Vinkius account to connect ChurchStamp to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup ChurchStamp with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate physical mailings in LangChain

`create_campaign` lets your LangChain agent use the ChurchStamp MCP Server to set up a new physical mail campaign and link it to a specific postcard design. The agent coordinates this tool call with other steps in your chain, feeding the output directly into subsequent tasks. Here's the deal: you trace the entire execution path in LangSmith to monitor latency and check payload sizes. If a contact import fails, the chain catches the error before triggering the postcard delivery.

Clean up member directories on the fly

`create_contact` adds new church members to your mailing list directly from your incoming data streams. Your LangChain agent parses unstructured emails or signup forms, extracts names and addresses, and inserts them into your directory. By combining this with database tools in a single chain, you keep your physical mailing list synchronized with your digital records. LangChain handles the state transitions, ensuring you never mail a postcard to an outdated address.

Verify MCP Server status before bulk runs

`check_churchstamp_status` confirms that the mailing API is fully operational before your agent starts generating expensive print jobs. This tool acts as an automated gatekeeper in your multi-step LangGraph pipelines. If the status check fails, the chain pauses execution and alerts your team, preventing wasted API calls. This basic check saves credit and keeps your automated outreach pipelines running predictably.

Setup guide

Set up ChurchStamp MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes ChurchStamp tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "churchstamp-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent ChurchStamp transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ChurchStamp. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect ChurchStamp now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about ChurchStamp MCP in LangChain

Use LangSmith to trace the exact tool call payload when `send_mail` executes. You can wrap the tool call in a standard try-catch block within your chain to handle API timeouts gracefully.

Yes, your agent can call `list_designs` to retrieve available templates, then use a LLM decision step to select the best match. The chosen design ID is then passed straight to `create_campaign` in the next link of the chain.

You initialize `MultiServerMCPClient` containing the ChurchStamp endpoint alongside your other servers. LangChain aggregates these tools, allowing your agent to pull member data from a database and immediately pass it to `create_contact`.

Call `get_user_details` at the start of your run to inspect your account balance. Your agent can read this balance and halt the pipeline if you lack funds for the current postcard batch.

All contact data processed by `create_contact` runs inside an isolated Vinkius V8 sandbox that destroys itself immediately after the tool execution finishes. No member addresses or postcard designs are stored on Vinkius servers, ensuring your church's directory remains strictly private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript