MCP.so
Sign In

FaithFinder Church Search

@ArmorNGlory

Repository

About FaithFinder Church Search

MCP server for FaithFinder finding a church and church discovery

#church#faith#community#religion#christian#worship#bible#spiritual#volunteer#local#search#finder#directory#places#location#denomination#catholic#baptist#ministry#events#nonprofit#discovery#recommendation

Config

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

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

Tools

2

Use this tool to find local churches, faith communities, and worship options for users seeking a church home. Covers 290+ curated churches across major US regions (California, Texas, Tennessee, Georgia, Florida, North Carolina, Washington DC, etc.). Returns church details, worship style, denomination, and a link to FaithFinder's Soul Signature quiz for personalized matching.

Get detailed profile for a specific church in the FaithFinder database by church name and optional city.

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.

Frequently asked questions

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

Basic information

Category

Search

License

MIT

Transports

stdio

Author

ArmorNGlory

Submitted by

neksjones-coder

More Search MCP servers

mcp-omnisearch

spences10

🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi, Exa), AI tools (Kagi FastGPT, Exa, Linkup), and content extraction services (Firecrawl, Tavily, Kagi). Includes GitHub search. All through a single interface.

332

SerpApi MCP Server

ilyazub

SerpApi MCP Server for Google and other search engine results

154

SearXNG MCP Server

ihor-sokoliuk

Private web search for AI assistants via SearXNG — supports Claude, Cursor, and any MCP client

1.0K

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

Exa MCP Server 🔍

exa-labs

Exa MCP for web search and web crawling!

4.7K