The church-mcp server provides tools to explore Kenya's religious institutions, community services, and welfare programs:
catholic_diocese_finder: Find Kenya's Catholic dioceses, parishes, and welfare services, with optional filtering by county.
protestant_denomination_guide: Get details on major Protestant denominations (ACK, PCEA, AIC, SDA, Methodist, Pentecostal, NCCK) and their services.
muslim_community_guide: Find Muslim communities, organizations (SUPKEM, CIPK), major mosques, and halal services, with optional county filtering.
religious_community_services: Discover welfare and social services offered by religious institutions, including education, health, and dispute resolution.
church_legal_registration: Get guidance on legally registering a religious organization in Kenya.
community_welfare_guide: Access information on food, medical, bursary, and counselling programs offered by religious communities, with optional filtering by need.
Note: All data is labeled DEMO and is not suitable for operational decisions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@church-mcp Find Catholic dioceses in Nairobi"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Faith institutions run a substantial share of Kenya's schools, clinics and welfare programmes, but their service directories are fragmented by denomination. For someone seeking help, the relevant question is what is nearby and open, not who runs it.
Related MCP server: familia-mcp
pip install church-mcpcatholic_diocese_finder —
args: county
protestant_denomination_guide —
args: no arguments
muslim_community_guide — Return Muslim community organisations, mosques, and welfare services in Kenya.
args: county
religious_community_services —
args: no arguments
church_legal_registration —
args: no arguments
community_welfare_guide —
args: need
from church_mcp.server import denomination_directory
result = denomination_directory()
# denominations, structures, welfare programmes, contactsAdd to claude_desktop_config.json:
{
"mcpServers": {
"church-mcp": {
"command": "python",
"args": ["-m", "church_mcp.server"]
}
}
}Directory information compiled from public sources and changes as institutions do. Confirm services and contacts directly before travelling to a facility.
Every tool response carries a source field. Responses labelled DEMO are
illustrative reference data, not a live feed — verify against the authority
named in the response before acting on it.
How to access Kenya religious community welfare programs. DEMO.
| Name | Required | Description | Default |
|---|---|---|---|
| need | No | Optional filter for need. Pass None to return all results. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no behavioral details beyond the title and does not disclose any side effects, permissions, or return behavior. The 'DEMO' tag may hint at non-production data, but it is not a sufficient behavioral disclosure. With annotations present, the description contributes minimal extra value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of a single sentence. However, the inclusion of 'DEMO' is extraneous and does not serve the agent's understanding. While front-loaded with the core purpose, the brevity sacrifices completeness and leaves out useful details. Not every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one optional parameter, no siblings, output schema exists), the description is still incomplete. It does not explain how the results are structured, what 'accessing programs' means operationally, or the range of possible values for 'need.' The output schema may fill some gaps, but the description itself lacks sufficient context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single parameter 'need,' which is well-documented in the schema. The tool description does not mention the parameter or provide additional context beyond the schema. Per the guidelines, the baseline is 3 when schema coverage is high, and no extra meaning is added.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'How to access Kenya religious community welfare programs.' It specifies the verb 'access' and the resource 'Kenya religious community welfare programs,' making the action and target unambiguous. However, the addition of 'DEMO' introduces slight ambiguity about the tool's production readiness.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool versus alternatives. There are no sibling tools, so differentiation is not required, but the description does not explain typical use cases or prerequisites for using the guide. The lack of usage context limits the agent's ability to decide when to invoke this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.4catholic_diocese_finderchurch_legal_registrationcommunity_welfare_guide1 field changedInput schema / properties / need / descriptionAdded value: +"Optional filter for need. Pass None to return all results."muslim_community_guideprotestant_denomination_guidereligious_community_servicesv0.1.0catholic_diocese_finderchurch_legal_registrationcommunity_welfare_guidemuslim_community_guideprotestant_denomination_guidereligious_community_servicesWith only one tool, there is no risk of confusion or overlap. The single tool is clearly distinct by default.
A single tool makes naming consistency trivial. The name 'community_welfare_guide' follows a clear noun_noun pattern, but there is no inconsistency to evaluate.
A server named 'church-mcp' with only one tool is far too few for the implied scope of church-related operations. Even as a DEMO, it feels thin and incomplete.
The tool is a single guide about welfare programs. For a church server, obvious gaps exist (e.g., events, donations, memberships, prayer requests). The 'DEMO' label reinforces the lack of completeness.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Find a Christian church by worship style, denomination, language, and location. Read-only.
Faith tools for AI agents: cited KJV Scripture, ORA Q&A, sermons, churches, prayer & giving.
Deterministic eligibility checker for grants, jobs and scholarships in Africa.
Real licensed Kenyan doctors, pharmacy and groceries. AI discovery only, payment held in escrow.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabrielmahia/church-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server