Bring Church Software
to VS Code Copilot
Learn how to connect Text In Church to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Text In Church data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 5 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Text In Church in VS Code Copilot
Text In Church and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Text In Church to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.