javaConf

This MCP server exposes a tool named getJavaConferences that scrapes conference data from a public GitHub repository (javaconferences/javaconferences.github.io) and presents it as structured JSON. The tool can return conferences for a specific year or default to the current year if no year is provided. Typical outputs include conferenceName, date, location, isHybrid, cfpLink, cfpDate, link, and country. To use the server, connect your MCP client to the server endpoint and invoke getJavaConferences with an optional year parameter. For example, asking for conferences in 2025 will return a list of 2025 events, while omitting the year will fetch the current year’s conferences if available. The server is built with Spring Boot and leverages Maven for packaging.

Prerequisites:

• Java Development Kit (JDK 11+ recommended)
• Maven (3.x)
• Git

Installation steps:

1. Clone the repository: git clone https://github.com/miliariadnane/javaconf-mcp-server.git
2. Navigate to the project directory: cd javaconf-mcp-server
3. Build the project (skip tests if desired): mvn -DskipTests package
4. Run the server: java -jar target/javaconf-mcp-server-0.0.1-SNAPSHOT.jar The server will start with default configuration. You can override the data source URL by setting application properties or environment variables as described in configuration notes.

Optional: run with a specific Spring profile if needed: java -jar target/javaconf-mcp-server-0.0.1-SNAPSHOT.jar --spring.profiles.active=prod

Notes and tips:

• The server fetches conference data by parsing the README.md from the javaconferences/javaconferences.github.io repository. By default, it uses the raw README at https://raw.githubusercontent.com/javaconferences/javaconferences.github.io/main/README.md, but you can configure a different URL via application.properties.
• The provided tool getJavaConferences accepts an optional year (string). If the year is omitted or invalid, the current year is used when available in the source data.
• Ensure network access for the server to fetch and parse the Markdown data from the configured URL.
• If you need to customize the data source, update application.properties with a new README URL, or add caching if needed for performance.
• Common issues: JVM memory configuration, missing jar due to mismatched build version, or incorrect path to the jar in the MCP client configuration. Verify paths and environment variables when launching.
• The MCP client (e.g., Claude Desktop) should point to the server’s host:port and reference the javaConf-mcp-server within its mcpServers configuration.