Model Context Protocol (MCP) - Developer Reference

This document outlines the Model Context Protocol (MCP) integration specifications for Jain Muni Locator. Publishing MCP server endpoints enables client LLMs (such as Gemini or Claude) and agentic coding workflows to programmatically query, traverse, and integrate JML’s monastics, temples, and location database.

---

1. Protocol Architecture

The Jain Muni Locator MCP Server operates over Stdio transport or SSE (Server-Sent Events) transport, exposing resources and tools mapped to backend JSON APIs.

graph LR
    subgraph Client Application
        LLM[Client LLM / Agent]
    end
    subgraph JML MCP Server
        Engine[MCP Protocol Engine]
        Tools[Exposed Tools]
        Resources[Exposed Resources]
    end
    subgraph JML Backend Database
        MySQL[(Laravel DB)]
    end

    LLM <-->|Model Context Protocol| Engine
    Engine <--> Tools
    Engine <--> Resources
    Tools <--> MySQL
    Resources <--> MySQL

---

2. Exposed Tools

MCP Tools allow the client model to execute actions and queries on behalf of users.

search_monastics

Search for Digambara Jain Monks and Nuns by name, alias, title, or current chaturmas location.

• Parameters:
  • query (string, required): Search term matching name or location.
  • only_alive (boolean, optional): Filter for living ascetics. Default is false.
• Response: A structured array of matching monastics including IDs, titles, and current locations.

get_monastic_profile

Retrieve full biography details, parent names, education, and authored books for a specific ascetic by ID.

• Parameters:
  • preacher_id (integer, required): Preacher profile ID.
• Response: Complete biography object including birth details, history, and publications.

search_temples

Search for Digambara Jain Temples on the map.

• Parameters:
  • query (string, required): Search term matching temple name or address.
• Response: Matching temples with coordinates and contact details.

submit_location_update

Submit a crowdsourced travel (vihar) update suggestion for a monastic.

• Parameters:
  • preacher_id (integer, required): Preacher ID.
  • location_name (string, required): Name of the current location (e.g. temple or town).
  • lat (number, optional): Latitude coordinate.
  • lng (number, optional): Longitude coordinate.
  • source_url (string, optional): Verification link or reference.

---

3. Exposed Resources

MCP Resources expose structured raw data streams that client models can read.

• preachers://{id}/profile: Returns the complete verified JSON:API representation of the ascetic’s profile.
• temples://{id}/details: Returns coordinates, history, and image references for the specified temple.
• preachers/active-chaturmas: Returns a list of all monastics currently observing Chaturmas along with their current location.

---

4. Claude Desktop & Agent Integration

To connect an LLM agent to the Jain Muni Locator database, add the server to your claude_desktop_config.json (or equivalent client configurations):

{
  "mcpServers": {
    "jain-muni-locator": {
      "command": "node",
      "args": [
        "d:/pankaj_codebase/jainmunilocator/mcp-server/index.js"
      ],
      "env": {
        "JML_API_URL": "http://127.0.0.1:8000/api/v2",
        "JML_API_TOKEN": "your_secure_developer_token_here"
      }
    }
  }
}