Realm MinistryPlatform MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REALM_MP_PASSWORD | Yes | Your Realm MinistryPlatform password | |
| REALM_MP_USERNAME | Yes | Your Realm MinistryPlatform username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify credentials work. If this fails, all other tools will too. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity between tools.
The single tool name 'health_check' follows snake_case consistently, and there are no other tools to cause inconsistency.
A single health check tool is extremely thin for a server named 'Realm MinistryPlatform MCP', which implies a much richer set of operations.
The server only provides credential verification, missing all expected CRUD and lifecycle operations for a ministry platform, making it severely incomplete.