How to Use the ChurchStamp MCP in Cursor

Build church management tools fast by injecting live ChurchStamp data straight into Cursor.

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 Cursor

Create your Vinkius account to connect ChurchStamp to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Code mail features with an MCP Server

ChurchStamp hooks your code editor directly into your direct mail API. When you build a new admin dashboard, Cursor's agent mode calls `list_campaigns` to pull real payload structures. You stop guessing what the JSON response looks like because the AI sees the actual data. Writing the creation logic happens in seconds. The agent drafts the exact POST request needed by testing `create_campaign` in the background. It maps the correct design IDs from `get_design` right into your source code.

Integrate congregation contact lists

This MCP Server feeds real member records into your development environment. Building a directory view is trivial when Cursor executes `list_contacts` to grab live names and addresses. Your AI writes the frontend components based on actual schema requirements. Adding new members gets the same treatment. You ask the editor to write a signup form, and it wires up the submit button using the exact parameters required by `create_contact`. Real context prevents broken API calls.

Test physical mail delivery in Cursor

Verifying your postcard logic usually requires a messy sandbox environment. Here, Cursor runs `check_churchstamp_status` to ensure your keys work before you write a single line of code. It acts as a live debugger for your external services. Triggering a test run is just a chat prompt away. The agent executes `send_mail` to confirm your newly written function actually dispatches the postcard. You watch the network request succeed without leaving your IDE tabs.

Setup guide

Set up ChurchStamp MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the ChurchStamp MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent ChurchStamp transactions." If the MCP tools are loaded correctly, Cursor will call the ChurchStamp tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "churchstamp-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Cursor

Create an mcp.json file in your project root directory. Paste the ChurchStamp endpoint details inside the mcpServers object. Toggle Agent mode on in the chat panel to activate the tools.

The agent fetches live template data while you type. It calls list_designs to see your available artwork and injects those specific IDs into your frontend components. Mock data becomes entirely unnecessary.

Reading docs takes you out of the editor. This setup lets the AI read the exact endpoints and test them live. Code generation gets significantly more accurate when the agent has real responses.

You control the scope of the integration. Placing the config file in your home directory makes it available everywhere. Keeping it in the project root restricts access to that specific repository.

Member names and physical addresses route directly from your machine to the API provider. The Vinkius MCP zero-trust architecture ensures no middleman stores your contact payloads. Your campaign drafts vanish from memory the moment the request finishes.

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