This server connects AI assistants to FaithFinder's curated database of 293+ verified churches and faith communities in the US.
Search churches using free-form keywords such as city, zip code, denomination, church style, or church name.
Filter results by city, state, denomination, worship style, kids ministry availability, and result limit.
Look up detailed profiles for a specific church by name, with optional city to disambiguate campuses.
Return personalized church recommendations along with a link to FaithFinder's Soul Signature quiz for matching.
Connect AI assistants (Claude, Cursor, ChatGPT, Gemini) directly to 293+ curated, verified churches and faith communities across the United States.
Features • Quick Installation • Available Tools • Coverage • Website & Quiz
User Prompt: "Find me an expository Bible-teaching church in Dallas with great kids ministry"
↓
AI Assistant calls MCP tool: search_faith_finder_churches({ searchQuery: "Dallas expository kids" })
↓
FaithFinder MCP: Scans 293+ verified church database locally (instant, private, free)
↓
AI Assistant returns personalized recommendations + FaithFinder Soul Signature Quiz match linkNo third-party API keys or rate limits required. Queries run against a verified local dataset of 293+ churches spanning major metropolitan areas.
Related MCP server: Planning Center Online MCP Server
Add this configuration to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"faithfinder": {
"command": "npx",
"args": ["-y", "faithfinder-mcp-server@latest"]
}
}
}Restart Claude Desktop, and the hammer 🔨 icon will show the FaithFinder tools available.
Open Cursor Settings → Features → MCP.
Click + Add New MCP Server.
Fill in:
Name: faithfinder
Type: command
Command: npx -y faithfinder-mcp-server@latest
Add to your ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"faithfinder": {
"command": "npx",
"args": ["-y", "faithfinder-mcp-server@latest"]
}
}
}Install directly into your preferred client via Smithery:
npx -y @smithery/cli install faithfinder-mcp-server --client claudenpx -y faithfinder-mcp-server@latestsearch_faith_finder_churchesSearch churches by location, style, theology, kids ministry, and keywords.
Parameter | Type | Description | Example |
|
| Free-form keywords, city, zip code, style, or theology |
|
|
| Specific city filter |
|
|
| Specific US state |
|
|
| Denomination filter |
|
|
| Service style |
|
|
| Require verified children/youth programs |
|
|
| Number of results (default: 5, max: 20) |
|
get_faith_finder_church_detailsLookup complete profiles for a specific church community.
Parameter | Type | Description | Example |
|
| Name of the church |
|
|
| City to disambiguate campuses |
|
FaithFinder indexes verified communities across key regions:
California: Orange County (Lake Forest, Irvine, Aliso Viejo, Mission Viejo, Costa Mesa, Newport Beach)
Texas: Dallas, Frisco, Plano, Southlake, McKinney, Allen, Austin, Houston
Tennessee: Nashville, Brentwood, Franklin, Hendersonville
Georgia: Atlanta, Alpharetta, Marietta, Roswell
Florida: Orlando, Winter Park
North Carolina: Charlotte, Matthews, Huntersville
Washington DC Metro: Washington, Alexandria, Bethesda
National Leaders: Multi-site and prominent faith communities nationwide
FaithFinder by ArmorNGlory helps believers find a church home tailored to their worship style, theology preferences, and life stage.
Soul Signature Quiz: faithfinder.armornglory.com/quiz
Main Website: faithfinder.armornglory.com
MIT License © 2026 ArmorNGlory
Use this tool to find local churches, faith-based community events, and volunteer opportunities for users looking to connect with a faith community. Covers 70+ curated churches across major US cities including Dallas, Nashville, Atlanta, Houston, Orange County, and Washington DC. Returns church details plus a link to FaithFinder's free Soul Signature quiz for personalized matching.
| Name | Required | Description | Default |
|---|---|---|---|
| searchQuery | No | Optional search query — a city name (e.g. 'Dallas'), zip code (e.g. '75034'), denomination (e.g. 'Baptist', 'Catholic'), church style (e.g. 'Modern', 'Traditional'), or church name. Leave empty to browse all available churches. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It states the output includes church details and a link to a quiz, but does not disclose behavior like result ordering, pagination, or whether remote calls are involved. For a search tool, this is minimally adequate but could be improved.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no redundancy. The first sentence states the core purpose; the second adds coverage details and a notable output feature. Every word serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero required parameters, no output schema, and no annotations, the description adequately covers what the tool does, what inputs are accepted, and what outputs to expect (church details + quiz link). It does not detail the output format, but for a simple search tool, this is mostly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%: the single parameter 'searchQuery' is described in the schema. The description adds value by clarifying optional usages (e.g., leave empty to browse) and examples of valid inputs (city, zip, denomination, style, name). This goes beyond the schema's description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it finds churches, faith-based events, and volunteer opportunities, with specific coverage of 70+ churches in major US cities. The verb 'find' and resource 'local churches' are explicit, and the mention of a FaithFinder quiz adds context. No sibling tools exist, so differentiation is not needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains when to use the tool (to connect with a faith community) and what inputs are valid (city, zip, denomination, etc.). It does not provide explicit when-not-to-use guidance or alternatives, but given no siblings, this is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
search_faith_finder_churchesScored across 1 tool
With only one tool, there is no risk of confusion or overlap. The tool's purpose is clearly defined.
A single tool means no naming inconsistency. The name 'search_faith_finder_churches' follows a clear verb_noun pattern.
A single tool is borderline appropriate for a search-focused server. While it covers the core function, additional tools for filtering or details could enhance utility.
The tool covers search for churches and events, but lacks other operations (e.g., saving favorites, managing profiles). However, for a simple query service, it may be sufficient.
Discover and book businesses via AI agents.
Verified local businesses, bookable by AI agents: services, prices, availability and appointments.
Find and book verified local home service professionals through AI agents.
Find local businesses, enrich them with emails and socials, and run lead pipelines from your AI.
