MCP Kotlin Server Sample

Created By
wujingwea year ago
Overview

what is MCP Kotlin Server Sample?

MCP Kotlin Server Sample is a sample implementation of a Model Communication Protocol (MCP) server in Kotlin, showcasing various server configurations and transport methods for both JVM and WASM targets.

how to use MCP Kotlin Server Sample?

To use the MCP Kotlin Server Sample, you can run the server on either the JVM or using Kotlin/WASM on Node.js. Start the server and connect using the MCP inspector to interact with it.

key features of MCP Kotlin Server Sample?

  • Multiple server operation modes including Standard I/O and SSE (Server-Sent Events) server.
  • Multiplatform support for both JVM and WASM.
  • Built-in capabilities for prompts management, resources handling, and tools integration.

use cases of MCP Kotlin Server Sample?

  1. Demonstrating real-time communication using SSE.
  2. Managing prompts and resources in a server environment.
  3. Supporting tool management for various applications.

FAQ from MCP Kotlin Server Sample?

  • What programming language is used for the server?

The server is implemented in Kotlin.

  • Can I run the server on different platforms?

Yes! The server supports both JVM and WASM platforms.

  • How do I connect to the server?

Start the server and use the MCP inspector to connect to http://localhost:<port>/sse.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wujingwe
Star
0
Language
Kotlin
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago