Java Server SDK Installation
AI-Powered Install
MCP Install
Follow the MCP Getting Started guide to quickly set up the DevCycle MCP server and connect your AI tool.
- Run this prompt:
"Install DevCycle into this app"
📦 Install in Cursor
📦 Install in VS Code
claude mcp add --transport http devcycle https://mcp.devcycle.com/mcp
Requirements
This version of the DevCycle SDK works with Java 11 and above.
Using the Java SDK library requires Maven or Gradle >= 7.6+ to be installed.
An x86_64 or aarch64 JDK is required for Local Bucketing with the DevCycle Java SDK.
Currently Supported Platforms are:
| OS | Arch |
|---|---|
| Linux (ELF) | x86_64 |
| Linux (ELF) | aarch64 |
| Mac OS | x86_64 |
| Mac OS | aarch64 |
| Windows | x86_64 |
In addition, the environment must support GLIBC v2.16 or higher. You can use the following command to check your GLIBC version:
ldd --version
The Java SDK on Local Bucketing mode uses the wasmtime-java binding, which does not work with Docker Alpine images at this time. If working with Docker, use a non-Alpine Linux image for Local Bucketing or use Cloud Bucketing mode.
Maven
You can use the SDK in your Maven project by adding the following to your pom.xml:
<dependency>
<groupId>com.devcycle</groupId>
<artifactId>java-server-sdk</artifactId>
<version>[2.9.3,3.0.0)</version>
<scope>compile</scope>
</dependency>
This range accepts compatible releases from 2.9.3 up to, but not including, 3.0.0. Refer to Maven Central for the latest available release.
Gradle
Alternatively you can use the SDK in your Gradle project by adding the following to build.gradle:
implementation("com.devcycle:java-server-sdk:[2.9.3,3.0.0)")
DNS Caching
The JVM, by default, caches DNS for infinity. DevCycle servers are load balanced and dynamic. To address this concern,
setting the DNS cache TTL to a short duration is recommended. The TTL is controlled by this security setting networkaddress.cache.ttl.
Recommended settings and how to configure them can be found here.