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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago