pickfit

BrowseMCP servers

kotlin-lib-mcp

MCP server exposing Maven Kotlin/Java library sources, API signatures, and KDoc to AI clients.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: JDK 25+, Java 25+ runtime
  1. download JDK 25 Temurin tarball via Adoptium API

    curl -L --fail -o /tmp/jdk.tar.gz "https://api.adoptium.net/v3/binary/latest/25/ga/linux/x64/jdk/hotspot/normal/eclipse"
  2. extract JDK to /tmp/jdk and verify java -version

    mkdir -p /tmp/jdk && tar -xzf /tmp/jdk.tar.gz -C /tmp/jdk --strip-components=1 && /tmp/jdk/bin/java -version
  3. download kotlin-lib-mcp release zip v0.10.1 from GitHub

    curl -L --fail -o /tmp/kotlin-lib.zip "https://github.com/aoreshkov/kotlin-lib-mcp/releases/download/v0.10.1/kotlin-lib-mcp-server-0.10.1.zip"
  4. unzip release zip to /tmp

    mkdir -p $HOME/.local/bin
    unzip -q -o /tmp/kotlin-lib.zip -d /tmp
    export JAVA_HOME=/tmp/jdk && export PATH=$JAVA_HOME/bin:$PATH
    /tmp/kotlin-lib-mcp-server-0.10.1/bin/server --help
  5. create wrapper script in ~/.local/bin that sets JAVA_HOME and execs server

    cat > $HOME/.local/bin/kotlin-lib-mcp-server <<'EOS'
    #!/bin/sh
    export JAVA_HOME=/tmp/jdk
    export PATH="$JAVA_HOME/bin:$PATH"
    exec /tmp/kotlin-lib-mcp-server-0.10.1/bin/server "$@"
    EOS
    chmod +x $HOME/.local/bin/kotlin-lib-mcp-server
    $HOME/.local/bin/kotlin-lib-mcp-server --help

Check that it works

export JAVA_HOME=/tmp/jdk && export PATH=$JAVA_HOME/bin:$PATH
/tmp/kotlin-lib-mcp-server-0.10.1/bin/server --version

The output should contain “kotlin-lib-mcp 0.10.1”.

Add it to your agent

claude mcp add kotlin-lib-mcp -- $HOME/.local/bin/kotlin-lib-mcp-server --transport stdio
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "kotlin-lib-mcp": {
      "command": "sh",
      "args": [
        "-c",
        "exec \"$HOME/.local/bin/kotlin-lib-mcp-server\" --transport stdio"
      ]
    }
  }
}

Add kotlin-lib-mcp-server --transport stdio as an MCP server in your AI client, then ask it to use the library tools such as fetch_library.

What it does

  • Fetch the real sources of Maven libraries
    How to use it
    1. Connect your MCP client to kotlin-lib-mcp-server --transport stdio.
    2. Call the fetch_library tool with a Maven coordinate, for example {"coordinate":"<group>:<artifact>:<version>"}.
    3. Read the returned text and resource link for the fetched library.
    Tested
  • See a library's public API and KDoc
    Not shown working
  • Read and search library source code
    Not shown working
  • Compare versions and public API changes
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 1 of 4 features work
  4. Needs the network

Good for

  • fetch and cache a Maven library for analysis
  • get resolved signature of a declaration by name
  • read KDoc for a library declaration
  • compare public API between two library versions
  • search raw library source and read implementation

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Needed the network
  • Checked on 1 Nov 2026
  • Version 0.10.1

An MCP client handshake over stdio listed 12 tools, and a call to fetch_library returned a result.

Differences the test machine hit

  • README: Requires JDK 25+ runtime
    In the test: No JDK preinstalled; manually downloaded Temurin JDK 25.0.5 tarball from api.adoptium.net and extracted to /tmp/jdk, set JAVA_HOME
  • README: claude mcp add kotlin-lib -- /path/to/kotlin-lib-mcp-server-<version>/bin/server --transport stdio
    In the test: Created wrapper ~/.local/bin/kotlin-lib-mcp-server that exports JAVA_HOME=/tmp/jdk before exec; direct bin/server needs JAVA_HOME set to JDK 25

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.