Aoirint MCPing Server

Overview

The Aoirint MCPing Server is an MCP (Model Context Protocol) service designed to give AI assistants instant, authenticated access to the live status of Minecraft Bedrock and Java servers. It solves a common pain point for developers building game‑centric chatbots or monitoring tools: the need to poll server status, parse response packets, and store historical data while keeping that information secure behind API keys. By exposing a clean RESTful interface that follows MCP conventions, the server lets an AI client retrieve real‑time player counts, latency, and version details without having to embed the ping logic inside the assistant itself.

At its core, the server performs three key functions. First, it pings any number of Minecraft servers across both Bedrock and Java editions, using the native ping protocol to gather uptime, player count, version string, and latency. Second, it persists this data in a PostgreSQL database so that historical trends can be queried and visualised. Third, it offers a web API protected by read/write API keys, allowing fine‑grained access control: read‑only clients can fetch status snapshots, while write clients can add or remove monitored servers. The use of Docker Compose and pre‑built images simplifies deployment, making it straightforward to spin up a production‑ready instance in minutes.

The server’s feature set is tailored for developers who need reliable, low‑latency status checks within AI workflows. Typical use cases include:

• Chatbot game lobbies: An assistant can answer “Is the Bedrock server online?” or “How many players are on the Java server?” by calling the MCP endpoint, then incorporate that response into a conversational reply.
• Operational dashboards: Combine the MCP API with an AI summariser to generate daily uptime reports or alerts when a server goes down.
• Event planning: Use the player‑count data to trigger an AI‑generated notification when a server reaches a certain threshold, such as announcing a special event to active players.

Integration with AI assistants is straightforward: the assistant issues an MCP request, receives a JSON payload containing server status, and then uses its own natural‑language generation to present the information. Because the MCP server handles authentication, rate limiting, and data persistence, developers can focus on higher‑level logic rather than boilerplate networking code.

What sets this MCPing Server apart is its dual‑edition support (Bedrock 1.20.x and Java 1.20.x) combined with a robust persistence layer. Many existing ping utilities only return transient data or lack version‑specific handling, but this service guarantees accurate packet parsing for the latest Minecraft releases. Additionally, the API’s key‑based security model aligns with MCP best practices, enabling secure multi‑tenant deployments where different teams or projects can share the same infrastructure without exposing sensitive endpoints.