calendar-mcp

What is calendar-mcp?

calendar-mcp is a Quarkus-based MCP server that integrates with Google Calendar via Apache Camel and leverages LangChain4j for AI capabilities. It is built on the Quarkus framework and is intended for developers who need a contextual protocol server for calendar management.

How to use calendar-mcp?

Run the application in development mode with ./mvnw quarkus:dev. For production, package with ./mvnw package and execute java -jar target/quarkus-run.jar. An über‑jar can be built with mvnw package -Dquarkus.package.jar.type=uber-jar. A native executable can be created using ./mvnw package -Dnative.

Key features of calendar-mcp

• Integration with Google Calendar via Apache Camel
• AI capabilities through LangChain4j Core
• Runs on Quarkus (Supersonic Subatomic Java Framework)
• Supports development mode with live coding
• Can be packaged as an über‑jar or native executable

Use cases of calendar-mcp

• Managing calendar events through a protocol‑driven server
• Combining calendar data with AI‑powered insights
• Automating calendar operations in containerized environments

FAQ from calendar-mcp

What runtime dependencies does calendar-mcp require?

calendar-mcp depends on Java (Quarkus runtime) and optionally GraalVM for native compilation. It uses Camel Google Calendar and LangChain4j libraries.

Can calendar-mcp be run as a native executable?

Yes, by executing ./mvnw package -Dnative and then running ./target/calendar-mcp-1.0.0-SNAPSHOT-runner. A container‑based native build is also supported.

How is calendar-mcp packaged?

The standard package produces a quarkus-run.jar along with dependency JARs in target/quarkus-app/lib/. An über‑jar (self‑contained) can be built with the uber-jar type flag.

Does calendar-mcp provide any AI features?

It includes LangChain4j Core integration, which can be used to add AI capabilities such as natural language processing or chat interactions.

What transport or authentication does calendar-mcp use?

The README does not specify transport or authentication details. It only mentions integration with Google Calendar via Camel, which typically uses OAuth 2.0.