Listed from the MCP registry; nobody on Odel publishes it. Is this yours? Claim @ac0ai
Find a Christian church by worship style, denomination, language, and location. Read-only.
One address for any MCP client. No sign-in needed on this server.
3 read
Grouped by tool name. At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Find the right church before your first visit.
Free global church guide with worship-aware profiles, built with Next.js 16, OpenNext on Cloudflare Workers, Cloudflare D1, Spotify, and YouTube.
Solo-maintained project, and my first open source project. This repository is public so people can report bugs, suggest improvements, and send small focused pull requests. I am still learning the open source side of things, so patience and clarity help a lot.
https://gospelchannel.comsitemap.xml, robots.txt, and structured dataPrerequisites:
If you use nvm, run:
nvm use
Install and start:
pnpm install
cp .env.example .env.local
pnpm dev
Helpful commands:
pnpm lint
pnpm build
pnpm smoke
pnpm check:env
Cloudflare D1 is the canonical database. The Worker uses the GOSPEL_D1
binding in wrangler.jsonc; it does not need a database URL or API token.
Local development uses an isolated local D1 database by default.
pnpm db:migrate:local
pnpm dev
Node maintenance jobs use GOSPEL_D1_DATABASE_ID, CLOUDFLARE_ACCOUNT_ID,
and GOSPEL_D1_API_TOKEN (or the existing CLOUDFLARE_API_TOKEN). The token
needs Account / D1 / Edit for jobs that write. Missing credentials fail closed.
For local jobs, an existing wrangler login can supply a refreshed token
without saving a second secret:
node scripts/with-d1-wrangler-auth.mjs node scripts/check-d1-access.mjs
Create a versioned SQL migration with pnpm db:new-migration -- descriptive_name,
keep the Drizzle models in src/db/d1-schema in sync, and apply with
pnpm db:migrate after checking the configured remote database. Production
imports must apply 0000_initial.sql, load data, then apply the remaining
migrations so derived search triggers do not rewrite imported source rows.
All active maintenance/import scripts use D1, including the Supabase-export
importer. Node scripts use the same D1 account, database ID and token as scheduled
jobs; there is no Postgres driver or fallback. Run local commands through
with-d1-wrangler-auth.mjs when using the Wrangler login. Use pnpm exec tsx
for scripts which import TypeScript modules.
After a schema change, regenerate the Node field codecs with
pnpm db:script-types; the test suite checks that they match the Drizzle schema.
Live integration tests require GOSPEL_D1_VERIFY_REMOTE=1 in addition to D1
credentials, so ordinary tests never query production implicitly.
You do not need every external integration to read the code or work on docs and UI.
Typical local development:
NEXT_PUBLIC_SITE_URLNEXT_PUBLIC_MEDIA_BASE_URLBETTER_AUTH_URLBETTER_AUTH_SECRETpnpm db:migrate:localNeeded for specific integrations and production-like flows:
YOUTUBE_API_KEYSPOTIFY_CLIENT_IDSPOTIFY_CLIENT_SECRETAPIFY_TOKENANTHROPIC_API_KEYBREVO_API_KEYCRON_SECRETAdmin access is database-backed. Promote an account to admin with:
pnpm db:seed -- --emails=you@example.com
Notes:
pnpm build uses offline mode for the content pipeline..env.local. Do not commit them.Ideas, bug reports, and small PRs are welcome.
If you want to help, the easiest path is:
Best ways to help:
See CONTRIBUTING.md for the short version of how this repo is run.
Please do not post security issues publicly. See SECURITY.md.
The production app is deployed on Cloudflare Workers via OpenNext. Contributors usually do not need deployment access.
Maintainer deploy command:
pnpm deploy
src/data/manual/ for cases where API data is limited or unavailable.MIT. See LICENSE.