test-mcp-server

Created By
bodguya year ago
Repository for test MCP server
Overview

what is test-mcp-server?

The test-mcp-server is a repository designed for testing purposes of a Minecraft server, allowing developers to experiment and develop features in a controlled environment.

how to use test-mcp-server?

To use the test-mcp-server, clone the repository from GitHub and follow the setup instructions provided in the README file to configure your local testing environment.

key features of test-mcp-server?

  • Easy setup for local Minecraft server testing
  • Support for various Minecraft server configurations
  • Ability to test plugins and modifications in a safe environment

use cases of test-mcp-server?

  1. Testing new Minecraft plugins before deploying them to a live server.
  2. Experimenting with server configurations without affecting a production environment.
  3. Developing and debugging custom Minecraft modifications.

FAQ from test-mcp-server?

  • Is test-mcp-server free to use?

Yes! The test-mcp-server is open-source and free for anyone to use.

  • Can I contribute to the test-mcp-server?

Absolutely! Contributions are welcome. Please check the contribution guidelines in the repository.

  • What version of Minecraft does this server support?

The test-mcp-server is designed to support multiple versions of Minecraft, but please refer to the documentation for specific version compatibility.

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