churchleader.guide
Read-only MCP access to a registry of church and ministry leadership guides
churchleader.guide is an MCP server for mentoring. It runs as a hosted remote server, so there is nothing to install locally.
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add --transport http guide-registry https://churchleader.guide/mcpAdd to Settings → Connectors → Add custom connector
https://churchleader.guide/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"guide-registry": {
"url": "https://churchleader.guide/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"guide-registry": {
"type": "http",
"url": "https://churchleader.guide/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"guide-registry": {
"serverUrl": "https://churchleader.guide/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://churchleader.guide/mcpEnter a Name (for example "churchleader.guide"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"guide-registry": {
"type": "http",
"url": "https://churchleader.guide/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
About churchleader.guide
The Bicycle Guide registry exposes a published collection of leadership guides through a read-only MCP endpoint. Its entries cover leading a church or ministry, leading teams and organisations, and leading inside a specific field, with the registry also listing homes, a subject taxonomy and a capability spine that tie the guides together.
An AI client connects to the streamable HTTP endpoint without authentication and can browse the published guides and their structure. The companion website presents the same material by subject and notes where sources disagree on a point.
The server suits people building assistants or research tools around ministry and church leadership content, who want a clean, citable source of guides rather than scraped web pages.
What it does
- Read-only guide access
- The endpoint lets clients read published guides without being able to change them.
- No authentication required
- The registry entry lists no auth, so clients can connect directly over streamable HTTP.
- Subject taxonomy
- Guides are organised by a taxonomy that groups them under subjects such as church leadership and team leadership.
- Capability spine
- A capability structure links guides together across the registry.
- Named source disagreements
- The website flags points where its sources disagree rather than presenting one view as settled.
Good for
- Pulling leadership guidance on volunteers, money or staff into a church-focused assistant
- Browsing guides by subject to find material for a ministry training course
- Letting an AI client cite published guides when answering leadership questions
churchleader.guide FAQ
Does the MCP server require an API key?
No. The registry entry lists no authentication.
Can the server modify guides?
No. The server is described as read-only.
How many guides are there?
The website links to 18 guides under its main section.
How do I add churchleader.guide to Claude Code?
Run this command in your terminal: claude mcp add --transport http guide-registry https://churchleader.guide/mcp
What are the best alternatives to churchleader.guide?
The closest alternatives to churchleader.guide are babyname.guide, Bicycle, careleader.guide, clinicalleader.guide and constructionleader.guide.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.