Releases: QTSurfer/mcp-java
Releases · QTSurfer/mcp-java
0.3.0
Changed (BREAKING)
- Auth model swapped from JWT-in-env to apikey-via-SDK. The MCP server now
reads a long-lived API key fromQTSURFER_APIKEY(or the new--apikey
flag) and usescom.qtsurfer:sdk-java
0.5.0QTSurfer.auth(apikey)to mint and transparently refresh a short-lived
JWT for the lifetime of the process. MCP servers can now run for days under a
desktop client without manual token rotation. - Removed: the
QTS_TOKENenv var and the--tokenCLI flag. There is no
backwards-compatibility shim — adopters must update their MCP client config
to passQTSURFER_APIKEYinstead. - Fail-fast startup: if
QTSURFER_APIKEYis missing or the initial JWT
exchange returns 401, the server logs a clear error to stderr and exits
non-zero before exposing any tools. Better than silently exposing tools that
all 401 on first call. - Maven coordinates:
<artifactId>renamed frommcptomcp-javato
match the GitHub repository name. This affects the on-disk JAR name
(mcp-java-0.3.0.jarinstead ofmcp-0.2.1.jar); distribution to end users
is unchanged — the GitHub Release asset is still
qtsurfer-mcp-java-0.3.0.jar.
Upgrade guide
Replace QTS_TOKEN with QTSURFER_APIKEY in every MCP client config snippet:
{
"mcpServers": {
"qtsurfer": {
"command": "/path/to/qtsurfer-mcp",
- "args": ["--url", "https://api.qtsurfer.com/v1"],
- "env": { "QTS_TOKEN": "<your-jwt>" }
+ "env": { "QTSURFER_APIKEY": "<your-api-key>" }
}
}
}Issue a new long-lived API key via the QTSurfer web app — the server handles
JWT minting and refresh for you.
0.2.1
fix: rename binaries to platform names before upload (asset name = fi…
0.2.0
Changed
- Maven coordinates migrated to
com.qtsurfer:mcp-javavia JitPack custom domain (git.qtsurfer.com). Consumers should replacecom.github.QTSurfer:mcp-javawithcom.qtsurfer:mcp-java:0.2.0. - Java packages renamed from
net.qtsurfer.mcptocom.qtsurfer.mcpthroughout. - Dependency on
com.qtsurfer:sdk-java:0.4.1. - Tags no longer use the
vprefix; CI release workflow updated accordingly.