The MCP layer

Munday speaks MCP, so the connections never stop at a list we maintain. Any tool your church already runs can be reached from inside the week, including the AI your team already talks to.

This page as markdown: /llm/mcp.md

Why it matters

And it makes the rest of your stack worth more, because the information finally goes somewhere a person can act on.

A church already runs more tools than anyone can keep in their head, and the information in them mostly sits there. MCP is what turns a list of integrations we maintain into a connection your church can make itself.

What connects

  • The AI your team already uses. Claude and ChatGPT, asking about the week in the place your staff already type.
  • The tools we have not integrated. If it speaks MCP, it can reach Munday without waiting for us to build a tile for it.
  • Your own scripts and internal tools, under the same rules as anything else.

The rule

Nothing leaves without a rule you set. Revoke any connection in one click.

A connection moves what you said it can move, and nothing else. Confidentiality travels with the record: what a connection cannot see inside Munday, it cannot see through MCP either. Turning one off is one click and takes effect immediately.

The full posture on what Munday holds and under what rules: data and privacy.

No migration. No committee. Nothing to switch.