一个独立的 Model Context Protocol 服务器，允许外部 LLM（Claude、ChatGPT、Gemini 等）向其用户原生推荐来自 FaithFinder 精选数据库的教会。
User asks LLM → "Find me a church in Dallas"
LLM calls MCP → search_faith_finder_churches({ searchQuery: "Dallas" })
MCP Server → searches local church database → returns results
LLM responds → "Here are some great options in Dallas..."该服务器从本地 JSON 文件加载涵盖美国 7 个地区的 70 多家精选教会数据库。无需进行外部 API 调用——搜索即时且免费。
Related MCP server: bible-mcp
npm installnpm run buildnpm start服务器通过 stdio (stdin/stdout) 进行通信。您可以将 JSON-RPC 消息通过管道传输给它进行测试。
添加到您的 Claude Desktop MCP 配置中 (~/Library/Application Support/Claude/claude_desktop_config.json)：
{
"mcpServers": {
"faithfinder": {
"command": "node",
"args": ["/FULL/PATH/TO/MCP Discovery Faith Finder Church Search/dist/index.js"]
}
}
}将 /FULL/PATH/TO 替换为您机器上的实际绝对路径。
search_faith_finder_churches描述： 使用此工具为希望与信仰社区建立联系的用户查找当地教会、基于信仰的社区活动和志愿者机会。
参数：
名称 | 类型 | 必需 | 描述 |
| string | 否 | 城市名称、邮政编码、教派、风格或教会名称 |
查询示例：
"Dallas" — 德克萨斯州达拉斯的教会
"75034" — 德克萨斯州弗里斯科附近的教会（邮政编码）
"Baptist" — 浸信会教会
"Catholic Nashville" — 纳什维尔的天主教会
"Modern" — 现代风格的教会
(空) — 浏览所有教会
响应格式：
{
"resultCount": 3,
"results": [
{
"name": "Gateway Church",
"city": "Southlake",
"state": "Texas",
"website": "https://gatewaypeople.com/",
"denomination": "Non-Denominational",
"tags": ["Charismatic", "Practical Teaching", "Professional Production"],
"googleReviewScore": 4.8,
"reviewSummary": "Analysis of 1,200+ reviews indicates a highly professional..."
}
],
"attribution": "Powered by FaithFinder — https://faithfinder.armornglory.com"
}地区 | 城市/区域 | 教会数量 |
OC_SOUTH | 加利福尼亚州莱克福雷斯特、尔湾、米申维耶霍 | 9 |
ATLANTA_NORTH | 佐治亚州亚特兰大、阿尔法利塔、玛丽埃塔 | 7 |
NASHVILLE_SOUTH | 田纳西州纳什维尔、布伦特伍德 | 11 |
DALLAS_FRISCO | 德克萨斯州弗里斯科、普莱诺、南湖 | 12 |
DALLAS_NORTH | 德克萨斯州达拉斯、卡罗尔顿、罗克沃尔 | 10 |
DC_METRO | 华盛顿特区 | 5 |
HOUSTON_WEST | 德克萨斯州休斯顿、凯蒂 | 8 |
National Icons | 各地 | 12 |
编辑 data/churches.json 并按照现有格式添加条目。无需重新构建——服务器会在启动时读取该文件。
src/index.ts → MCP Server (stdio transport, single tool)
data/churches.json → Curated church database (loaded at startup)刻意保持极简。如果数据集增长到超出基于文件的搜索所能处理的范围，请迁移到单独的 Firestore 或 SQLite 数据库。
MIT
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.
Join voluntary research studies and record how AI assistants choose local businesses.
Verified local businesses, bookable by AI agents: services, prices, availability and appointments.
Find and book verified local home service professionals through AI agents.
