Python MCP Server

Created By
sisovina year ago
The **python-mcp-server** project is a Flask-based web server designed to interact with Minecraft, likely as part of a larger system for managing Minecraft servers, plugins, or player data.
Overview

what is Python MCP Server?

Python MCP Server is a Flask-based web server designed to interact with Minecraft, serving as a backend for managing Minecraft servers, plugins, or player data.

how to use Python MCP Server?

To use Python MCP Server, install the dependencies, configure the server settings, and start the Flask application. Access the web interface at http://localhost:5000.

key features of Python MCP Server?

  • User authentication for server admins and players.
  • Database integration using SQLAlchemy for storing user data and server settings.
  • A web interface with dynamic content served through HTML and Jinja2 templates.
  • API endpoints for fetching player data and executing server commands.
  • Unit testing for various components of the server.

use cases of Python MCP Server?

  1. Minecraft Server Dashboard for admin management.
  2. Player Stats Tracker for monitoring achievements and ranks.
  3. Plugin Backend for integrating with Minecraft plugins.

FAQ from Python MCP Server?

  • Can I use Python MCP Server for any Minecraft server?

Yes! It is designed to work with various Minecraft server setups.

  • Is there a web interface available?

Yes! The server provides a web interface for easy management.

  • How do I run the server?

Install dependencies, configure settings, and run the Flask app using python server/main.py.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sisovin
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