tachyon: Skill for Claude Code

Tachyon MCP Server Skill️

Make Java 21+ MCP server. Tachyon lib. Transport = Streamable HTTP (Netty).

Dependency

Import tachyon-bom once, then add modules with no <version>:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>dev.tachyonmcp</groupId>
            <artifactId>tachyon-bom</artifactId>
            <version>1.0.0-beta.25</version> <!-- get latest version from Maven Central -->
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

<dependencies>
    <dependency>
        <groupId>dev.tachyonmcp</groupId>
        <artifactId>tachyon-core</artifactId> <!-- or tachyon-kotlin for the Kotlin DSL -->
    </dependency>
</dependencies>

Core

• TachyonServer.builder() → ServerBuilder. Start here.
• .build() (only terminal method) → TachyonServer (AutoCloseable), no transport bound yet.
• TachyonServer.start() (blocking) → binds the Netty transport.
• TachyonServer: .tools(), .resources(), .prompts(), .tasks(), .completions() first; then .start(), .port() (throws before .start()), .close(), .config().
• Dynamic registration: .tools().register(...), .resources().register(...), .prompts().register(...), .completions().registerForPrompt(...)/.registerForResource(...) — all work before or after .start().
• Every function gets dev.tachyonmcp.api.runtime.InteractionContext → protocol + optional session + notifications.
• ⚡ Virtual threads: All synchronous functions (ToolFn, ResourceFn, PromptFn, CompletionFn) run on a virtual thread per request. Blocking for I/O is fine — never use synchronized (pins carrier thread). Use ReentrantLock instead.

Quickstart

var server = TachyonServer.builder()
    .info(b -> b.name("my-server").version("1.0"))
    .port(8080)
    .build();
server.start();
// server.port() → real bound port (matters when port=0); throws before start()