Build with NearFaith

NearFaith is a free church-finder directory — 15,403 listings across 1,786 cities as of September 2026, each with service times, denomination, contact details, and groups. Everything below is offered at no cost to anyone building an assistant, app, or website that needs accurate church data or wants to show it on a church's own site.

Tools

All four tools are annotated read-only, non-destructive, and idempotent.

Try it with curl

Initialize a session, then call a tool. The server is stateless, so there's no session id to carry between calls — each request stands alone.

curl -s -X POST https://www.nearfaith.com/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-client","version":"1.0"}}}'

curl -s -X POST https://www.nearfaith.com/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"find_churches","arguments":{"city":"Queen Creek","state":"AZ","limit":3}}}'

Adding it to an MCP client

Most current MCP clients speak Streamable HTTP directly — look for a setting called something like "remote MCP server," "custom connector," or "server URL" and point it at the endpoint above. A generic config looks like this:

{
  "mcpServers": {
    "nearfaith": {
      "url": "https://www.nearfaith.com/api/mcp"
    }
  }
}

For a stdio-only client that can't speak Streamable HTTP directly, bridge with mcp-remote:

{
  "mcpServers": {
    "nearfaith": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.nearfaith.com/api/mcp"]
    }
  }
}

We can't make vendor-specific promises about how any particular assistant surfaces remote MCP servers in its own settings — check that client's own documentation for the exact steps.

Drop this where the widget should appear. It's a plain <script>, not an iframe, so it works on older church WordPress sites and isn't blocked by an X-Frame-Options header. It also adds a small "Powered by NearFaith" link back to the church's listing.

<div id="nearfaith-embed"></div>
<script src="https://www.nearfaith.com/embed/<your-church-id>" async></script>

The id is specific to your church's claimed listing — copy the ready-to-use snippet (with the id already filled in) from your listing's manage dashboard once you claim it. Haven't claimed your church yet? Claim it free →

The widget is cached and refreshes hourly, so it stays fast on the host page without hitting NearFaith on every visitor.