MCSS MCP Server

Created By
largeorbitalobjecta year ago
Model Context Protocol server for MCSS (Minecraft Server Soft)
Overview

what is MCSS MCP Server?

MCSS MCP Server is a Model Context Protocol server designed for managing Minecraft servers through the MCSS (Minecraft Server Software) API, enabling seamless interaction with Minecraft servers using MCP clients like Claude Desktop.

how to use MCSS MCP Server?

To use the MCSS MCP Server, clone the repository, set up a virtual environment, install the required dependencies, and configure the server settings in a .env file. Then, integrate it with Claude Desktop for management functionalities.

key features of MCSS MCP Server?

  • Server Management: List, control, and manage Minecraft servers, execute commands, and view console output.
  • Backup Management: Create and manage backups for Minecraft servers.
  • Scheduler Management: Schedule and manage tasks for server actions and backups.

use cases of MCSS MCP Server?

  1. Managing multiple Minecraft servers from a single interface.
  2. Automating server backups and maintenance tasks.
  3. Executing commands and monitoring server performance in real-time.

FAQ from MCSS MCP Server?

  • What are the prerequisites for using MCSS MCP Server?

You need Python 3.10 or higher, MCSS with Web API enabled, and an API key.

  • Is MCSS MCP Server free to use?

Yes! It is open-source and available for free.

  • How can I contribute to the project?

Contributions are welcome! You can submit a Pull Request on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
largeorbitalobject
Star
0
Language
Python
License
MIT 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