DelmADS-Notifications

# DADS Notifications MCP Server on Spring Boot for sending notifications to Telegram. It rises as an [MCP](https://modelcontextprotocol.io/)-server (Spring AI MCP Server) and provides tools that MCP-client (e.g., Claude) can use to send messages to users through a Telegram bot. The project is being developed as part of the infrastructure of the pet project **DADs** - Delm Aggregation Data System, and in the future, it will serve as an integration point for sending notifications. ## Stack - **Java 22**, **Spring Boot 4.0.7** (Gradle, Kotlin DSL) - **Spring AI MCP Server** (WebMVC) - **Telebof** — Telegram Bot API client - **PostgreSQL** + **MyBatis**, migrations — **Liquibase** - **Actuator** + **Micrometer** (Prometheus) - **Lombok** ## Configuration All secrets are set via environment variables (file `.env`, not committed to the repository — it's in `.gitignore`). | Variable | Purpose | |----------------|---------------------------| | `TG_BOT_TOKEN` | Telegram bot token | | `DB_ADDRESS` | `host:port` PostgreSQL | | `DB_NAME` | database name | | `DB_USER` | database user | | `DB_PASSWORD` | database password | Example `.env`: ```dotenv TG_BOT_TOKEN=123456:ABC-DEF... DB_ADDRESS=localhost:5432 DB_NAME=dads_notifications DB_USER=postgres DB_PASSWORD=postgres ``` ## Running ```bash ./gradlew bootRun # run locally ./gradlew build # build and run tests ``` By default, the server currently runs in **MCP stdio** mode (`spring.ai.mcp.server.stdio=true`): it is launched by the MCP client, and communication occurs via stdin/stdout. ## Development The workflow (branches, commits, releases) is described in [CONTRIBUTING.md](CONTRIBUTING.md).