Basic Minecraft Protocol (MCP) Server

Created By
cs-flytbasea year ago
A basic MCP (Minecraft Protocol) server implementation
Overview

what is Basic Minecraft Protocol (MCP) Server?

The Basic Minecraft Protocol (MCP) Server is a simple implementation of a Minecraft Protocol server in Python, designed to allow Minecraft clients to detect the server in the server list through basic handshake and status response protocols.

how to use Basic Minecraft Protocol (MCP) Server?

To use the MCP Server, clone the repository, make the script executable, and run the server. Connect to it using a Minecraft client by adding the server address.

key features of Basic Minecraft Protocol (MCP) Server?

  • Basic MCP protocol implementation
  • Handshake packet processing
  • Server status response
  • Simple client disconnect handling
  • Multi-threaded client handling

use cases of Basic Minecraft Protocol (MCP) Server?

  1. Hosting a basic Minecraft server for testing purposes.
  2. Learning about network programming and server-client architecture.
  3. Developing further enhancements for a more complete Minecraft server experience.

FAQ from Basic Minecraft Protocol (MCP) Server?

  • What programming language is used for the server?

The server is implemented in Python.

  • Are there any external dependencies?

No, the server uses standard Python libraries only.

  • What are the limitations of this server?

It only implements handshake and status response packets and does not handle full login or gameplay.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cs-flytbase
Star
0
Language
Python
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)

a day ago