Magisterium MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGISTERIUM_API_KEY | Yes | Your Magisterium API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| magisterium_queryA | Send a query to the Magisterium API to get authoritative Catholic Church teaching responses with citations |
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 potential for confusion between tools. The tool's purpose is clearly defined and distinct.
The tool name follows a clear verb_noun structure with 'magisterium_query' indicating the domain and action. With a single tool, there is no inconsistency to worry about.
The server has a single tool, which is slightly under the typical range but appropriate for its narrow scope of querying the Magisterium API. One tool feels justified given the focused purpose.
The tool covers the core need of querying for authoritative Church teaching responses with citations. Additional tools could explore related resources, but the current surface is functional for its intended use.