@churchify/mcp

An MCP server that exposes the Churchify church-retention platform as tools an AI agent (Claude, Codex, etc.) can call — "which guests haven't we followed up with, and create a call task for each."

It runs over stdio and talks to the Churchify REST API with an API key, so it inherits exactly the scopes that key was granted.

Configure in an MCP client

{
  "mcpServers": {
    "churchify": {
      "command": "npx",
      "args": ["-y", "@churchify/mcp"],
      "env": {
        "CHURCHIFY_API_URL": "https://api.churchify.app",
        "CHURCHIFY_API_KEY": "chy_xxx"
      }
    }
  }
}

Create an API key in Churchify under Admin → Settings → API Keys. Give read-only assistants a key scoped to retention.view; allow retention.manage only if the agent should create or complete tasks.

Environment

| Var | Default | Purpose | |---|---|---| | CHURCHIFY_API_KEY | — | API key (required to call any tool) | | CHURCHIFY_API_URL | http://localhost:9010 | Churchify REST API base URL | | CHURCHIFY_ACTOR_PERSON_ID | — | Optional person id for audit attribution |

Tools

| Tool | Purpose | Scope | |---|---|---| | retention_briefing | Church-wide pastor retention briefing | retention.view | | list_at_risk_people | People with retention risk + reasons | retention.view | | get_person_retention_brief | One person's score, reasons, next actions, timeline | retention.view | | list_person_next_actions | Pending next actions for a person | retention.view | | create_next_action | Create a retention task for a person | retention.manage | | complete_next_action | Mark a next action complete | retention.manage |

License

MIT © Moloks Technologies