MCP(Model Context Protocol) minimal Kotlin client server sample

Created By
takahiroma year ago
Overview

What is MCP Kotlin Minimal Client-Server Sample?

This project is a simple weather tool that demonstrates server-client interaction using the Model Context Protocol (MCP). It allows users to ask about the weather and receive responses from a server.

How to use MCP Kotlin Minimal Client-Server Sample?

To use this project, clone the repository from GitHub, set up the Kotlin environment, and run the client application. You can then ask questions like "What's the weather in Tokyo?" to receive responses.

Key features of MCP Kotlin Minimal Client-Server Sample?

  • Demonstrates client-server communication using MCP.
  • Allows querying of weather information.
  • Provides a structured flow for tool execution and response handling.

Use cases of MCP Kotlin Minimal Client-Server Sample?

  1. Asking for weather updates in various locations.
  2. Integrating with other tools that require server-client communication.
  3. Learning about the Model Context Protocol in practical applications.

FAQ from MCP Kotlin Minimal Client-Server Sample?

  • What programming language is used?

The project is developed in Kotlin.

  • Is this project suitable for production use?

No, this is a demonstration project and not intended for production use.

  • Where can I find the source code?

The source code is available on GitHub at https://github.com/takahirom/mcp-kotlin-minimal-client-server-sample.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
takahirom
Star
1
Language
Kotlin
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

5 hours ago