Bring Church Software
to Cursor
Learn how to connect Text In Church to Cursor and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Text In Church MCP Server?
Connect your Text In Church account to any AI agent and simplify how you manage your congregation directory, volunteer groups, and community outreach through natural conversation.
What you can do
- Member Management — List all church people and visitors, and add new members to your directory programmatically.
- Group Oversight — List church groups, volunteer lists, and ministries to keep your community organized.
- SMS Outreach — Send text messages to entire groups or specific individuals directly via AI commands.
- Keyword Tracking — List active keywords used for automated sign-ups and visitor responses.
- Visitor Engagement — Log new visitors and manage their contact data to ensure timely follow-ups.
- Communication Visibility — Monitor your outreach campaigns and group memberships directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Text In Church API Key (found in your developer settings)
3. Start managing your church communications from Claude, Cursor, or any MCP client
Who is this for?
- Church Administrators — quickly retrieve member lists and coordinate group announcements via simple AI queries.
- Pastors & Ministry Leads — send encouragement messages and verify visitor data directly from the workspace.
- Volunteer Coordinators — manage team groups and automate follow-ups with new members via the AI assistant.
Built-in capabilities (5)
Add a new person
List church groups
List active keywords
List people in the church directory
Send an SMS message
Why Cursor?
Cursor's Agent mode turns Text In Church into an in-editor superpower. Ask Cursor to generate code using live data from Text In Church and it fetches, processes, and writes. all in a single agentic loop. 5 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Text In Church in Cursor
Text In Church and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Text In Church to Cursor 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 Text In Church in Cursor
The Text In Church 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 5 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
Text In Church for Cursor
Every tool call from Cursor to the Text In Church MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send an SMS to a specific group using the AI?
Yes! Use the send_church_sms tool and provide the Group ID and your message content. Your agent will trigger the broadcast to all members of that group instantly.
How do I see all the active keywords for my church?
Run the list_church_keywords query. The agent will retrieve a complete list of keywords configured in your account for automated responses and sign-ups.
Is it possible to add a new visitor via AI?
Absolutely. Use the add_church_person action. Provide the first name, last name, and contact details (phone/email) to instantly register the new visitor in your directory.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.