Skip to content

CatholicOS/liturgical-calendar-mcp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Liturgical Calendar MCP Server

A Model Context Protocol (MCP) server that provides access to the Roman Catholic Liturgical Calendar API allowing retrieval of liturgical calendar data for any year, or for various nations, or dioceses.

The MCP server is a secure interface for AI assistants to access liturgical calendar data, providing a unified interface as a structured toolset for AI agents. This enables compliant AI systems (like ChatGPT MCP clients, LangChain agents, and custom LLM runtimes) to reason over liturgical dates, seasons, feasts, saints, and liturgical rankings with full contextual intelligence.

Purpose

This MCP server provides a secure interface for AI assistants to access liturgical calendar data from the Liturgical Calendar API maintained by Rev. John R. D'Orazio. It supports querying the General Roman Calendar, national calendars, and diocesan calendars with historical accuracy from 1970 to 9999.

Features

Current Implementation

  • list_available_calendars - List all available national and diocesan calendars with their locales and settings
  • get_general_calendar - Retrieve the General Roman Calendar for a specific year with optional locale
  • get_national_calendar - Retrieve the liturgical calendar for a specific nation (i.e. IT, US, NL, VA, CA...) and year
  • get_diocesan_calendar - Retrieve the liturgical calendar for a specific diocese and year
  • get_liturgy_of_the_day - Retrieve the liturgical celebrations for a specific date (or today if not specified), from any supported calendar
  • get_announcement_easter_and_moveable_feasts - Retrieve the announcement of Easter and the moveable feasts (aka Noveritis) as pronounced on Epiphany for a specific year for any supported calendar

Particular Celebrations Detection

When retrieving national or diocesan calendars, the server automatically identifies and highlights celebrations that are particular (unique) to that calendar:

  • Hybrid Detection Approach: Events are marked as particular using two methods:

    1. Event Key Comparison - Events whose event_key is not found in the General Roman Calendar
    2. Square Bracket Detection - Events with square brackets in their name (e.g., [USA], [Diocese of Rome])
  • Intelligent Filtering: Weekday events (grade 0) are automatically excluded from particular celebrations, as they represent minor liturgical differences that are not significant enough to highlight

  • Use Cases:

    • Identify patron saints specific to a nation or diocese
    • Discover local feast days and memorials
    • Compare regional liturgical variations
    • Plan liturgical celebrations with local context

This feature helps distinguish between universal celebrations (found in the General Roman Calendar) and regional celebrations particular to specific nations or dioceses.

Prerequisites

  • Docker Desktop with MCP Toolkit enabled
  • Docker MCP CLI plugin (docker mcp command)
  • No authentication required - the API is publicly accessible

Installation

For more detailed information, see the step-by-step instructions and screenshots provided in the project wiki: Setting-up-Docker-MCP-Toolkit.

  1. Install Docker Desktop

    Download and install Docker Desktop from https://www.docker.com/products/docker-desktop/.

  2. Enable Docker MCP Toolkit

    Open the Docker Desktop settings and enable the MCP Toolkit under the "Beta Features" tab. You should now see the "MCP Toolkit" icon in the Docker Desktop left sidebar. Perhaps try enabling a tool from the catalog as a proof of concept, for example "Obsidian". Then connect the MCP Toolkit to a client like Claude Desktop. After restarting Claude Desktop, when clicking on the "Tools" icon below the chat prompt, you should see an "MCP_DOCKER" category, and clicking on the arrow next to that you should see available tool calls (for example obsidian tool calls if you enabled the Obsidian tool from the Docker MCP catalog).

  3. Clone the repository

    git clone https://github.com/CatholicOS/liturgical-calendar-mcp.git
    cd liturgical-calendar-mcp
  4. Build the Docker image

    docker build -t liturgical-calendar-mcp .
  5. Update the Docker Desktop MCP catalog

Edit the file %USERPROFILE%\.docker\mcp\catalogs\docker-mcp.yaml, and paste this at the end:

  litcal:
    description: "Access Roman Catholic Liturgical Calendar data for any year, nation, or diocese from 1970-9999"
    title: "Liturgical Calendar"
    type: server
    dateAdded: "2025-10-22T00:00:00Z"
    image: litcal-mcp-server:latest
    ref: ""
    readme: ""
    toolsUrl: ""
    source: ""
    upstream: ""
    icon: ""
    tools:
      - name: get_general_calendar
      - name: get_national_calendar
      - name: get_diocesan_calendar
      - name: list_available_calendars
      - name: get_liturgy_of_the_day
      - name: get_announcement_easter_and_moveable_feasts
    metadata:
      category: integration
      tags:
        - catholic
        - liturgy
        - calendar
        - religious
      license: MIT
      owner: local

litcal should be a descendant of registry.

Edit the file %USERPROFILE%\.docker\mcp\registry.yaml, and paste this at the end:

  litcal:
    ref: ""

Again, litcal should be a descendant of registry.

No need to start any containers, Docker MCP Toolkit will spin up the tool container on demand when an agent attempts to access the tool.

Try with Claude Desktop: if it was already started, exit Claude Desktop completely (make sure it is not running in the background in the tray) and start it again.

You should now see the "Liturgical Calendar" tool in the tools list under MCP_DOCKER category.

Note

Docker MCP Toolkit only officially supports MCP servers already published in the online catalog, so every time you restart Docker Desktop it will remove any custom entries in the registry.yaml and catalogs/docker-mcp.yaml files. If you find that the tool calls suddenly stop working, you may have to manually update the registry.yaml and catalogs/docker-mcp.yaml files again.

Local Installation for Claude Desktop & VS Code

If you want to run the MCP server locally and integrate it with Claude Desktop or VS Code without the Docker MCP Toolkit, see CLAUDE_VSCODE_INSTALL.md for step-by-step instructions.

Configuration

The MCP server can be customized through a user configuration file. This allows you to adjust API endpoints, cache settings, and more without modifying the codebase.

Creating Your Configuration

  1. Copy the example configuration file:

    cp litcal.config.example.yaml litcal.config.yaml
  2. Edit litcal.config.yaml with your preferred settings:

    # API Configuration
    api_base_url: "https://litcal.johnromanodorazio.com/api/dev"
    default_timeout: 30
    
    # Cache Configuration
    metadata_cache_expiry_hours: 24
    calendar_cache_expiry_hours: 168
    cache_dir: "./cache"
  3. Your litcal.config.yaml file is automatically ignored by git and will not be committed.

Configuration Options

API Settings

  • api_base_url - Base URL for the Liturgical Calendar API (default: https://litcal.johnromanodorazio.com/api/dev)
  • default_timeout - Timeout for API requests in seconds (default: 30)

Cache Settings

  • metadata_cache_expiry_hours - How long to cache the list of available calendars (default: 24 hours)
  • calendar_cache_expiry_hours - How long to cache liturgical calendar data (default: 168 hours / 1 week)
  • cache_dir - Directory for cache files, absolute or relative to project root (default: ./cache)

Environment Variables

You can also override any configuration setting using environment variables (highest priority):

  • LITCAL_API_BASE_URL
  • LITCAL_DEFAULT_TIMEOUT
  • LITCAL_METADATA_CACHE_EXPIRY_HOURS
  • LITCAL_CALENDAR_CACHE_EXPIRY_HOURS
  • LITCAL_CACHE_DIR

Example:

export LITCAL_DEFAULT_TIMEOUT=60
python litcal_server.py

Configuration Priority

Settings are loaded in the following order (highest priority first):

  1. Environment variables
  2. User configuration file (litcal.config.yaml)
  3. Default settings (settings.py)

Usage Examples

In Claude Desktop, you can ask:

  • "List all available national liturgical calendars"
  • "Show me the liturgical calendar for the United States in 2024"
  • "What is the calendar for the Diocese of Rome for this year?"
  • "What liturgical events are celebrated in Canada?"
  • "What are the particular celebrations for Italy this year?"
  • "Show me the patron saints and local feasts for the Diocese of Boston"
  • "Get the liturgy of the day"
  • "Get the liturgy of the day for the Diocese of Rome"
  • "Get the liturgy of the day for the Diocese of Rome for 2024"
  • "Get the liturgy for September 8th 3036 for the United States"

Architecture

flowchart LR
  ClaudeDesktop --> MCPGateway --> LiturgicalCalendarMCPServer --> LiturgicalCalendarAPI
Loading

API Information

Calendar Types

General Roman Calendar

The universal calendar for the Roman Catholic Church

National Calendars

  • IT - Italy
  • US - United States
  • NL - Netherlands
  • VA - Vatican
  • CA - Canada

Diocesan Calendars

Various dioceses within national territories (use list_available_calendars to see all)

Development

Local Testing

# Run directly
python3.12 -m venv venv
source venv/bin/activate
pip install -r requirements.txt -r requirements-dev.txt
python litcal_server.py
# Ctrl+C to stop (you may have to do so a few times)

# Test MCP protocol
python test_mcp_list_tools.py | python litcal_server.py | jq
# This should output, in pretty-printed JSON format, the tools made available by the MCP server
# Ctrl+C to stop
# There are a few other similar test scripts for testing the various tool calls

Adding New Tools

  1. Add the function to litcal_server.py
  2. Decorate with @mcp.tool()
  3. Ensure all parameters have well defined types
  4. Method docstring should summarize the purpose of the tool, and explain how the parameters should be implemented, possibly offering a few examples; the LLM reads the docstring, which therefore gives it context on how to use the tool
  5. Return formatted strings with emojis
  6. Rebuild the Docker image

Troubleshooting

Tools Not Appearing

  • Verify Docker image built successfully: docker images | grep litcal
  • Check catalog and registry files for correct formatting
  • Ensure Docker Desktop MCP config files include the litcal tool
  • Restart Claude Desktop completely

Connection Errors

Invalid Calendar IDs

  • Use list_available_calendars to see valid nation and diocese codes
  • Nation codes must be uppercase ISO 3166-1 alpha-2 codes (IT, US, NL, VA, CA)
  • Diocese codes are lowercase with underscore (romamo_it, boston_us)

Data Accuracy

The Liturgical Calendar API strives for historical accuracy:

  • Based on original sources (Roman Missals, Vatican decrees)
  • Memorials and feast days only generated from their introduction year
  • Follows Mysterii Paschalis and other liturgical documents
  • Not copied from potentially inaccurate online sources

Liturgical Grades

Events are graded by importance (0-7):

  • 0 - Weekday
  • 1 - Commemoration
  • 2 - Optional Memorial
  • 3 - Memorial
  • 4 - Feast
  • 5 - Feast of the Lord
  • 6 - Solemnity
  • 7 - Higher Solemnity (takes precedence over regular solemnities)

Security Considerations

  • No authentication required (public API)
  • Running as non-root user in container
  • All data is read-only
  • No sensitive information handled

License

Apache 2.0 License

Credits

Liturgical Calendar API created and maintained by Rev. John R. D'Orazio API Documentation: Swagger UI


Note: This server accesses a development API endpoint. For production use, consider using the stable API endpoint when available.

🙏 Mission

This MCP server is part of a broader initiative to make the liturgical, biblical, and canonical patrimony of the Church accessible to AI systems in a faithful and structured way.

“Missionaries have always gone with Christ to new frontiers, while the Holy Spirit pushed and preceded them” (SR 17c). We can only regard this so-called new continent with the zeal of a Francis Xavier or a Mother Cabrini. — Cardinal Michael Czerny, A New World and a New Mission

About

An MCP (Model Context Protocol) server that will allow AI agents to interact with the Liturgical Calendar API.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 5