FaithFinder Church Search

Name: FaithFinder Church Search
Author: ArmorNGlory

@ArmorNGlory

Repository

About FaithFinder Church Search

MCP server for FaithFinder finding a church and church discovery

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "faithfinder": {
      "command": "npx",
      "args": [
        "-y",
        "faithfinder-mcp-server"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is FaithFinder Church Search?

FaithFinder Church Search is a standalone Model Context Protocol (MCP) server that enables LLMs like Claude, ChatGPT, and Gemini to recommend churches from a curated database. It loads a local JSON file with 70+ churches across 7 US regions, performs no external API calls, and delivers instant, free results.

How to use FaithFinder Church Search?

Install dependencies (npm install), build (npm run build), and test locally (npm start). For Claude Desktop, add a configuration entry in your MCP config file using the search_faith_finder_churches tool. Invoke the tool with an optional searchQuery argument (city, zip, denomination, style, or church name) to find churches, faith events, or volunteer opportunities.

Key features of FaithFinder Church Search

Single MCP tool for church search
Local curated database – no external API calls
70+ churches across 7 U.S. regions
Instant, free searches over stdin/stdout
Query by city, zip, denomination, style, or name
Editable JSON file – no rebuild required

Use cases of FaithFinder Church Search

Users ask an LLM to find churches in a specific city
Users request churches by denomination (e.g., Baptist in Nashville)
Users search for churches near a zip code (e.g., 75034)
Users browse all available churches with an empty query
LLM assistants provide recommendations with review summaries and website links

FAQ from FaithFinder Church Search

How does this compare to a church search that calls an external API?

FaithFinder uses a local JSON file – no network calls are made. Searches are instant and free, with no external service dependency.

What dependencies are required?

Node.js and npm. The server communicates over stdio (JSON-RPC) and is designed to work with MCP‑compatible LLM clients.

Where does the church data live?

The data is stored in data/churches.json, loaded at server startup. You can edit this file to add or update churches; no rebuild is needed.

Are there any limitations on the database size?

The file‑based search is intended for moderate datasets. If the database grows significantly, the README suggests migrating to Firestore or SQLite.

What transport does this server use?

It uses stdio (standard input/output) as the MCP transport. No HTTP or network transports are provided.

Comments

More Search MCP servers

Web Scout MCP Server

pinkpixel-dev

A powerful MCP server extension providing web search and content extraction capabilities. Integrates DuckDuckGo search functionality and URL content extraction into your MCP environment, enabling AI assistants to search the web and extract webpage content programmatically.

129