外部のLLM（Claude、ChatGPT、Geminiなど）が、FaithFinderの厳選されたデータベースからユーザーに教会をネイティブに推奨できるようにする、スタンドアロンのModel Context Protocolサーバーです。
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..."このサーバーは、米国の7つの地域にわたる70以上の教会を厳選したデータベースをローカルのJSONファイルから読み込みます。外部API呼び出しは行われないため、検索は即時かつ無料です。
Related MCP server: bible-mcp
npm installnpm run buildnpm startサーバーはstdio（標準入力/標準出力）を介して通信します。テストのために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 | ワシントンD.C. | 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.
