Church Website Audit by Journey Digital MCP server

Church Website Audit by Journey Digital

A free church website audit tool (an MCP server and Cursor plugin) that checks mobile, page speed, SEO basics, and whether a first-time visitor can find service times.

Real output of auditchurchwebsite for a public church homepage, run 2026-10-21. Finding text is shortened in the image; the full JSON is in docs/example-audit-redeemer.json.

Install

One line, from a clean checkout (Node 18+, zero dependencies). It clones the repo and runs the local self-test:

git clone https://github.com/tnvolman/jd-church-website-audit && cd jd-church-website-audit && node scripts/prove.js

Then point your MCP client at server/audit-mcp.js (see Usage). In Cursor, the repo also loads as a plugin through .cursor-plugin/plugin.json.

Prefer not to install anything? Run the same church website checker in your browser at journeydigital.ai/audit.

What it checks

One MCP tool, auditchurchwebsite, sends one church homepage to Journey Digital's audit and returns every check:

• Mobile: viewport tag, pinch-to-zoom, text size.
• Speed: Google PageSpeed mobile performance.
• SEO basics: title, meta description, H1, https, canonical link, robots.txt, sitemap.
• First-time guests: service times, street address, an I'm New / Plan a Visit path, map or directions.
• Contact and giving: tap-to-call, contact info, giving one click away.
• About and local identity: beliefs or about link, city in the title or main heading.
• Heads-up notes (never counted as a fail): menu size and menu labels.

Report the result as passed/total exactly as the API returns passed and total. Do not hardcode /21 and do not recompute the counts. Each check comes with a plain-English finding and a cited source for each check. It covers church website SEO basics only and does not guarantee any search ranking. Things like first-screen placement and how easy the phone menu feels still need a human look.

Usage

MCP client config (Claude Desktop, Cursor mcp.json, and similar):

{
  "mcpServers": {
    "church-website-audit": {
      "command": "node",
      "args": ["/absolute/path/to/jd-church-website-audit/server/audit-mcp.js"]
    }
  }
}

Then ask your agent: "Audit https://example-church.org with auditchurchwebsite."

Tool arguments:

Set JOURNEYDIGITALAUDITBASEURL to use another origin (default https://journeydigital.ai). There is no API key. If the audit service is unreachable or returns a malformed report, the tool returns an error; it never invents results.

Docker

The image speaks MCP over stdio. It is node:22-alpine, installs nothing, and runs as the node user:

docker build -t jd-church-website-audit .
docker run -i --rm jd-church-website-audit

Point the MCP client at that command. JOURNEYDIGITALAUDITBASEURL still overrides the origin.

Privacy

Shortened. The full README is on GitHub.